- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.7K Databases
- 221.9K General Database Discussions
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.3K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 466 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Buggy App – Simulate performance problems
Buggy App is a simple java application that simulates different performance problems like Memory Leak, OutOfMemoryError, CPU spike, thread leak, StackOverflowError, deadlock, unresponsiveness, …
Using this application, you can simulate various performance problems in your environment. Here are a few use cases where Buggy App can be used:
a. You can configure and launch Buggy App to consume high memory on the same server where your application is running. You can study under this circumstance whether your application’s SLA (Service Level Agreement) is impacted.
b. You can configure and launch Buggy App in a docker container to consume high CPU and see whether other containers on the same host are impacted or not.
c. If you are building performance tools or monitoring tools, you can simulate various performance degradations using Buggy App and see whether your tools address those performance probelms. (Infact we developed this BuggyApp to validate our root cause analysis tool yCrash behaviour.)
You can download
1. Buggy App from this location
2. Source code (if it’s of interest) from this location
To run Buggy App, you will need Java 8 or above version installed.
Here are the performance problems that you can simulate through Buggy App:
1. OutOfMemoryError: Java heap space
To generate ‘java.lang.OutOfMemoryError: Java heap space’ launch Buggy App with following arguments:
java -Xmx512m -jar buggyApp.jar PROBLEM_OOM
2. Memory Leak
If you would like to simulate a memory leak without experiencing OutOfMemoryError, then launch Buggy App with the following arguments.
java -jar buggyApp.jar PROBLEM_MEMORY
When you launch the Buggy App with these arguments, 80% – 90% of the allocated memory will be consumed. But it will not result in OutOfMemoryError.
3. CPU spike
If you would like the CPU consumption to go up to 80 – 90% then launch the Buggy App with following arguments:
java -jar buggyApp.jar PROBLEM_CPU
4. Thread Leak
If you would like the application to keep slowly spawning new threads, then launch the Buggy App with the following arguments.
java -jar buggyApp.jar PROBLEM_THREADLEAK
When you launch the Buggy App with these arguments eventually ‘java.lang.OutOfMemoryError: Unable to create new native thread’ will be generated.
If you would like the application to experience Deadlock, then launch the Buggy App with the following arguments.
java -jar buggyApp.jar PROBLEM_DEADLOCK
6. Stackoverflow Error
If you would like the application to experience ‘java.lang.StackOverflowError’, then launch the Buggy App with the following arguments.
java -jar buggyApp.jar PROBLEM_STACKOVERFLOW
7. Blocked Threads
If you would like to put multiple threads in BLOCKED state, then launch the Buggy App with the following arguments.
java -jar buggyApp.jar PROBLEM_BLOCKED