Top 10 J2EE performance problems
When i read top 10 j2ee problem in vincent blog http://blog.xebia.com/2007/04/30/ejapp-top-10-countdown-wrap-up/
- #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
I think not all that list is true. i disagree point 1 and 4
e.g point number 1, off course this mistake is in design phase not part of J2EE. You shold blame your system analyst or your DBA for this.
point number 4, is adding a library to our application. i think if we put library we dont needed in our apps does not impact the performance, cause library we dont need is idle unless we use it.
|