Normally in any java application this virtual memory issues can be found by using the operating system utility called VMSTAT. If the memory in JVM machine is low then the application will take too long for GC (garbage collection). There is one more alternative to find out the reason if your application is very low in memory is Java.Lang.OutofMemory exceptions. Systems will through java.lang.outofmemory exceptions if the application is low in memory. So memory related problems can be found by using ‘Heap size’, ‘verbose garbage collection’, or by ‘VMSTAT’.
Friday, December 14, 2007
How to find Virtual memory bottle necks in Load runner?
Posted by
Performance Testing Loadrunner Faqs
at
1:31 PM
Labels: bottle necks, bottlenecks, cpu bottlenecks, cpu related issues, different bottlenecks, performance bottle necks, virtual bottlenecks, virtual memory, virtual memory issues
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment