DBORA for Developers

Most of the performance problems we find in the field are caused by decisions made by application developers. Developing a high-performance application is tough work. Most of your training focuses on the functional aspects of your development environment. What little attention is paid to making scalable use of your underlying Oracle technology is often misguided.

Too often, tuning begins when an application’s development is already finished. This is unfortunate because it implies that performance is not as important as other crucial requirements of the application. Performance is not merely optional, though; it is a key property of an application. Not only does poor performance jeopardize the acceptance of an application, it usually leads to a lower return on investment because of lower productivity. You optimize the performance of an application to provide a benefit to a business, so when approaching performance problems, you have to understand the business problems and requirements before diving into the details of the application. Simply put, the aim of an application is to provide a benefit to the business using it. Consequently, the reason for optimizing the performance of an application is to maximize that benefit. As mentioned however this is an ideal situation as not much emphasis is placed on application performance during development.

The first thing to do when an application experiences performance problems is obvious: identify the root cause of the problem. Unfortunately, all too often this is where the real trouble starts. In a typical scenario where everyone is looking for the source of a performance problem, developers blame the database for poor performance, and the database administrators blame both the developers for misusing the database and the storage subsystem administrators because their very expensive piece of hardware ought to provide much better performance. And as the complexity of the application and infrastructure supporting it increases, so does the mess.

What if you could identify and eliminate scalability inhibitors in your application code before your application ever left your desk? Your users would get the most out of your software. Your applications would scale to enormous user counts and data volumes. And you'd have fewer performance bugs to fix hence fewer application performance problems.

KEY  BENEFITS

1. The method we promote identifies the application code that runs in the database tier and on other technology stack supporting the business for effective root cause performance analysis.

2. The method is response-time based performance improvement methodology that yields maximum economic value to your business.

3. The method is applicable for application already in production and application yet to be deployed into production.