Memory section

The following memory statistics are all interrelated and track each other.

Table 1. Memory section
REQTEXT
XML	Console Display	Description
`<MemoryListendSize>`	`Listend size`	The process current memory footprint as reported by the OS, in bytes. Typically this value must be under 20 MB.
`<MemoryListendMaxSize>`	`Listend max size`	The process max memory footprint size as reported by the OS, in bytes. This value fluctuates depending on various internal requirements. Typically, it tracks the current size with little deviation and is the high water mark indicator for it.
`<MemoryListendMemoryIn_use>`	`Listend memory in use`	The process current memory usage size, in bytes, based on its dynamically allocated memory requirements. This value grows, depending on its needs, to as much as 100 MB for internal packet buffers.
`<MemoryListendMaxMemoryIn_use>`	`Listend max memory in use`	The high water mark indicator for the above in use value.
`<MemoryReassdSize>`	`Reassd size`	The process current memory footprint size, in bytes, as reported by the OS. This value is the current memory that is allocated to it, including its footprint. It typically can range from a few megabytes to 1 GB or more.
`<MemoryReassdMaxSize>`	`Reassd max size`	The high water mark for the current memory size above.
`<MemoryReassdMemoryIn_use>`	`Reassd memory in use`	The process current memory usage size that is based on dynamically allocated memory demands from it. This value can also vary from a few megabytes to over 1 GB depending on its processing requirements for the current network traffic activity. There is no typical value, but it is usually less than 500 MB.
`<MemoryReassdMaxMemoryIn_use>`	`Reassd max memory in use`	The high water mark for the current memory size above.
`<MemoryListendOutputBuffers>`	`Listend output buffers`	Current memory used in output buffer, in bytes, for the listend process filtered packet traffic. This memory buffer is used to buffer traffic that is flowing from listend to reassdthrough its pipe. Reassd process pulls traffic packets as it is able to process them. The default size of this buffer is 100 MB.
`<MemoryListendOutputBuffersMax>`	`Listend output buffers max`	The high water mark for the above buffers size value.
`<MemoryDeliveryQueue>`	`Delivery queue`	Current hit delivery buffer size that is used, in bytes, to send hits through the socket to the Unica Discover server.
`<MemoryDeliveryQueueMax>`	`Delivery queue max`	The high water mark for above queue size value.
`<MemorySslSessionCacheEntries>`	`SSL session cache entries`	The current number of SSL session entries that are stored in the cache table. The conf config setting determines what the max limit of entries that can be stored at a time. Typical default is 10,000 entries. For more information on tuning the max limit setting, see SSL `Total session cache misses` stat below.
`<CpuUsagePctHigh>`	not available	CPU usage percent (high)
`<CpuUsagePctTotal>`	not available	CPU usage percent (total)
`<Id>`	not available	process ID in the context of DNCA processes
`<MemUsagePctHigh>`	not available	Memory usage percent (high)
`<MemUsagePctTotal>`	not available	Memory usage percent (total)
`<Name>`	not available	name of the process
`<ProcessCount>`	not available	ProcessCount
`<VirtualMemorySizeKbytesHigh>`	not available	Virtual memory size (kbytes) high
`<VirtualMemorySizeKbytesTotal>`	not available	Virtual memory size (kbytes) total