QueueMetrics > Running QueueMetrics

Large environment(s)

<< < (2/2)

QueueMetrics:
FYI: we usually do a major system test for QueueMetrics before an official release - we simulate an instance of QM going through about 600,000 real-time reports and 600,000 non real-time reports before shipping it.
 
This takes about a week and it is meant to make sure the RAM image is stable and there are no leaks at either the Java heap usage or the total RAM usage (and yes, it is possible in Java to leak RAM at the JVM level though not in the Java heap - we wncountered a casa where file descriptors would not free their own RAM under Linux, though they would under Win32).

Developing a server-side app meant for heavy-duty number crunching is not that easy, but surely this is needed for an industrial-grade solution.

Navigation

[0] Message Index

[*] Previous page