You can optionally clone the entire project from Git hub. The application is packaged as a WAR file and can be downloaded from the following link There are many use cases, you can customize it and let us know through comments. Test your monitoring tool (or) APM and an alerting system like Solarwinds, Splunk, ELK, AppDynamics etc.Simply create graphs and observe how CPU and Memory Usage reflect in JMX monitors like JConsole, VisualVM etc.Creating OutOfMemory Errors to test your ON OutOfMemory events or alerting system.Create CPU hogging threads and test your CPU performance.You can test which GC policy is effective and troubleshoot the GC issues. ![]() To test your JVM how it handles the load.These are the use cases I could think of but it is not limited to this. the app would create threads with specified interval until the maximum number of threads reach. How it works: Once deployed and ready, You can create CPU and memory consuming threads from the UI. What is it: A Web Application (WAR file) for consuming CPU and Memory on the server wherever deployed So what is it and how it works and what problem it is going to solve?. The objective of this article is to present and discuss the CPU and Memory Consuming WebApp for Java J2EE containers and Application servers like tomcat, jboss, Websphere, weblogic Invoking the Memory Consuming Monster and Validate it.Invoking the CPU Consuming Monster and Validating. ![]()
0 Comments
Leave a Reply. |