Tracking VAST memory usage in run-time

[davidg]

Hello,

we have multiple web servers in VAST which consume quite a lot of memory due to high user loads.

Sometimes it happens that junior programmers introduce a memory leak in the code which can cause the server image to grow over the size of available memory which slows down the servers.

So, I wanted to introduce a memory watchdog process which would keep track of memory usage changes and alarm the system administrator before things go wrong.

Getting the memory usage was easy, but when I wanted to add monitoring of the number of instances of specific classes I have noticed that in run-time evaluating "aClass allInstances size" will always answer 1.

Is there any way to make the method #allInstances working in run-time, or is there any other way to get the number of instances of a particular class?

[tc]

Hello,

AFAIK, allInstances should work. Do you see different results for a dev and runtime image? Does this happen for all classes or one particular class?

--tc

[waynej]

Some things you might find useful if the problem isn't always simply the number of instances of one class that you know ahead of time:

EsbTimer vmStats numberOfScavenges.
EsbTimer vmStats numberOfGlobalGCs.
EsbTimer vmStats millisecondScavengeTime.
EsbTimer vmStats millisecondGlobalGCTime.

EsMemoryUseReport
countAllMemoryUsingSelector: #countInstances
minCount: 1
minSize: 1
output: Transcript.

System totalAllocatedMemory.
System availableMemory.
System availableNewSpaceMemory.
System availableOldSpaceMemory.

"Unrelated, but can be interesting"
Processor allProcesses collect: [:aProcess |aProcess processName -> aProcess switchCount]