Developer Partner Community

  • November 10, 2014

10 tips for ADF Application (Module Pool) tuning By Niels Gorter

Juergen Kress
PaaS Partner Adoption

Performance tuning is one of the things that is often left behind during development. Project leaders and business owners seem to think it happens on its own or just push it to the background when the deadline comes close. Another thing that doesn’t help is that performance tuning for ADF applications is a more advanced topic. During a regular ADF training there’s so much to talk about there simply isn’t enough time to cover it, so people are left on their own to try and figure out how it works. There are also a lot of things that have an influence on performance like business demands and application user experience which may not be directly obvious. In this post I will give you 10 great tips on tuning to give you a starting point.

1. AM Pool tuning != Performance test one month before launch.
Often a performance or load test is scheduled just before launch, even after testing is complete. I see this a lot. You don’t want to do this. If you do find issues with performance it may well be that there are some fundamental things wrong with your application that you cannot fix and retest within the given timeframe. Your fix may even break performance or functionality in other places. In 90% of the cases where it is done this way you end up with your application in production anyway because of the deadlines causing a lot of users to be unhappy. Which does equal unhappy management.
2. Start early in the development phase
pretty much follows out of bullet number 1. Start early so when you do have wrong settings on VO’s or on the AM you don’t have to refactor the whole application and regular testing will tackle any issues you may introduce. Changing how your application is build is also a lot easier if it’s still small.
3. Get !someone! to actually tell you what you are tuning for
This is actually a lot harder than it sounds. I still see a lot of applications where the non-functional requirements, if there are any, hardly ever include anything on security or performance and expected user statistics. This information coupled with the expected amount of data that changes and gets stored is essential to how you tune your application. The numbers on data and it’s usage tell you something on how to organize your application and the numbers on user tells you how to set the numbers in your AM configuration. Try and get numbers on max logged in users, numbers of concurrent users, session times, how usage and load is spread across your application. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.