VBrick dme, Admin Manual

Page: 42 / 219

30 © Vbrick Systems, Inc.
This is a snapshot of the Memory Use in your system. Memory is measured as
your physical plus swap. Hovering your mouse over the measures will provide
detailed measures.
The field’s background color will change indicating its health status. The
available statuses are: Normal (0%-50% memory usage), Warning (51%-85%),
and Alert (> 85%). As a snapshot, this is a transient measure that may self-
correct. These thresholds are applied on snapshots and represent hard cut-offs
between the status – please consider your use cases, the status, and the actual
measure within the status to help determine if action is necessary.
Guidance : A DME, depending on load, shares it memory with all other system
services. When we examine the memory, we combine the system RAM and
SWAP because it is really a high measure of this combination that may indicate
issues. In most cases, the SWAP will have little use, but there are some use
cases that may drive it up. Because the memory measure includes SWAP it may
drive higher into Warning or Alert based on the frequency that the system
returns SWAP memory from running or terminating apps. In most cases, spikes
of memory use that drive Waring or Alert reflect singleton events within the
system, and may be transitory. Meaning, if your DME bounces into an out of
Warning or Alert, but does not remain in that state for more than 1 refresh of
the Status Bar, action may not be necessary but as a cautionary measure you
may wish to monitor the use and playback experiences.
This is a snapshot of the Content Disk Use . DMEs can be thought of as
having two logical partitions – an OS partition and the content partition. This
snapshot measures the content partition and does not include the OS partition.
The content partition, however, does include some system files. The field’s
background color will change indicating its health status. The available statuses
are: Normal (0%-75% usage), Warning (76%-85%), and Alert (> 85% OR less
than 32GB free). As a snapshot, this is a transient measure that may self-
correct. These thresholds are applied on snapshots and represent hard cut-offs
between the status – please consider your use cases, expansion of content plans
(disk growth can be fast or slow depending on content ingestion into Rev), the
status, and the actual measure within the status to help determine if action is
necessary.
Guidance : When evaluating the content disk size, please consider that this
partition is shared by a number of DME activities. This partition will include
not only (per configuration) new pre-positioned content, but also any content
that gets pre-positioned during normal use. The system swap file (which can be
several GB depending on your DME License) is contained within the content
space. Also, it should be noted that your Caching system will also utilize the
content store as well in accordance to the levels specified on the Streaming
page. So, if you mark your DME as a DEDICATED caching server, much disk
space will be used. It terms of guidance, it depends on your use case. If your
DME is used in a highly caching environment, then running at higher disk use
will automatically self correct. Also, even in a largely pre-positioned
environment, the DME will self correct – it will delete pre-positioned content
as it needs space. It will not, however, delete space that has been used by the
caching engine (which can be cleared on the Maintenance page). If you are
concerned about your disk availability, please review your Cache settings, pre-
position settings on Rev, and potentially add additional space through the DME
admin interface.