Posted by Robert van Loghem in the early morning: July 31st, 2007
Our fourth episode on the Enterprise Java Application Performance Top 10 is ready for download!
Security and Performance Expert Vincent Partington and Performance Expert Jeroen Borgers talk about the Enterprise Java Application Performance Top 10.
Discussed are numbers 4-Badly performing libraries.
More information about number 4 can be found here.
and for number 3-Incorrectly implemented concurrency see; here.
So download the podcast here or better yet! subscribe to one of our rss feeds on podcast.xebia.com
Posted by Robert van Loghem mid-morning: June 20th, 2007
On the 12th of june we interviewed Kirk Pepperdine (javaperformancetuning.com), Angelika Langer (Java Generics) and Jonas Boner (Terracotta) at the dutch J-Spring congress organized by the NL-JUG (dutch java user group).
You can download the episodes here or subscribe here.
We also have 2 interviews in dutch with Peter van Rijn (Refactoring to Patterns!) and Wouter Zelle (Kwaliteitsbewaking met sourcecode analysetool PMD) you can download those from our podcast page.
Posted by Robert van Loghem in the early morning: June 6th, 2007
Our third episode on the Enterprise Java Application Performance Top 10 is up for grabs!
Security and Performance Expert Vincent Partington and Performance Expert Jeroen Borgers talk about the Enterprise Java Application Performance Top 10.
Discussed are numbers 6-Improper Caching and 5-Excessive memory usage.
More information about number 6 can be found here.
and for number 5 see; here.
So download the podcast here or better yet! subscribe to one of our rss feeds on podcast.xebia.com
Posted by Robert van Loghem just before lunchtime: May 23rd, 2007
It’s wednesday again! and that means a new Xebia Podcast!
This week we continue the Enterprise Java Application Performance Top 10, numbers 8 and 7 with Vincent Partington and Jeroen Borgers.
Number 8 – Incorrect usage of Java EE
More information about number 8 can be found here.
Number 7 – Unnecessary use of XML
More information about number 7 can be found here.
So download the podcast here or better yet! subscribe to one of our rss feeds on http://podcast.xebia.com
Posted by Vincent Partington around lunchtime: April 30th, 2007
For the last two and a half months, I’ve been blogging about the Enterprise Java Application Performance Problems Top 10:
- #10 – Excessive logging
- #9 – Incorrect application server configuration
- #8 – Incorrect usage of Java EE
- #7 – Unnecessary use of XML
- #6 – Improper caching
- #5 – Excessive memory usage
- #4 – Badly performing libraries
- #3 – Incorrectly implemented concurrency
- #2 – Unnecessary remoting
- #1 – Incorrect database usage
Posted by Vincent Partington in the late afternoon: April 29th, 2007
I’ll keep you in suspense no longer. 
It’s time for numero uno of the EJAPP Top 10 countdown!
Somewhat unexpectedly for an Enterprise Java Application Performance Problems Top 10, the #1 issue is the incorrect usage of databases.
Posted by Vincent Partington in the late evening: April 25th, 2007
Picking up the pace to make sure I get the countdown finished before I go to JavaOne , I’ll quickly move on to #2 of the EJAPP Top 10 countdown….
While remoting is often used in Enterprise Java applications due to the fact that other systems and applications need to be invoked, unnecessary remoting is an important cause of badly performing Enterprise Java applications.
Posted by Vincent Partington in the early evening: April 22nd, 2007
We’ve reached the top 3 of the EJAPP Top 10 countdown now, so let’s get going…
Incorrectly implemented concurrency can cripple the performance of your application in very unpredictable ways. Applications that perform pretty well under light load may crawl to a halt under heavier load.
A major cause is lock contention, which only becomes an issue when multiple threads are involved. For example, if a request that takes 100ms, spends 25ms in a critical section, no more than four requests can be handled every 100ms. No matter how much you decrease the other 75ms, Amdahl’s law tells us the maximum speedup by introducing parallelization is 4!
Posted by Vincent Partington in the late evening: April 16th, 2007
After skipping the easter weekend to go snowboarding in Chamonix, I’ll continue the EJAPP Top 10 countdown with number 4.
Badly performing libraries are a problem that occurs more often than one would expect. This issue is somewhat similar to the incorrect usage of Java EE in that not enough care is taken in selecting and using a certain technology. Some development teams will happily pile JAR after JAR into their WEB-INF/lib directory or into their POM file, :
- without checking whether that library is really needed (and does not overlap with functionality already offered by other libraries used),
- without checking whether that library can offer good performance or whether a better performing alternative is available,
- without reading the documentation to see how it should properly be used, and
- without defining how the library is going to be used within the application
Posted by Vincent Partington in the early evening: April 2nd, 2007
We’ve covered half of the EJAPP Top 10 now. Now let’s start with the second half!
Excessive memory usage manifests itself in two ways:
- a large number of allocations (for short-lived objects), or
- a large number of objects per se.
Both can be problematic, not because of the allocations themselves but because of the effect on the garbage collector. Luckily garbage collection performance is improving with every JDK release.