Some Common Issues
Performance issues may occur in the following areas: database, memory, concurrency. Database-related headaches frequently include long response times, caching issues (either no caching, improper configuration and distribution), and an insufficient number of database connections. When it comes to memory, Stop-To-Wait (STW) garbage collections and memory leaks can make for an unpleasant experience. Meanwhile, concurrency can also get us in trouble with three thread-related issues: thread deadlocks, thread gridlocks, and thread pool configuration gridlocks.
All the problems outlined above inevitably affect the most important aspect of our apps – their performance. To help you sort through the wide range of advice for troubleshooting Java performance issues, we have chosen a few additional articles to get you started.
Ready to go an extra mile on your Java developer’s journey? Ready to go beyond what Eclipse has to offer? Try our fullstack MyEclipse IDE, which will rock your world.
How to Avoid Them
One list of tips comes from Thorben Janssen in his Dzone article – 11, to be precise, in which he warns us about unnecessary optimization and recommends to come up with a performance test, as well as tackle the most serious issues first, and much more.
Ten more coding specific tips on getting the most out of Java can be found on the Jooq.org blog: the use of StringBuilder, primitives and the stack, avoiding recursion, among others.