Performance tuning in adf and webcenter application

How good a website is often measured with the performance. Every one wants their website to work fast. In the Oracle world, it is very challenging because of the heavy software stack used.


Without having indepth knowledge of the stack it very hard to fine tune it.


I am still putting some pointers for improving the performance of a website in general. There are certain pointers that are focused mainly for Webcenter and ADF application.

•  Always enable client site caching. Browser caches the static data like css, javascript and images. So it will not downloaded the again and again from the server. These setting can be done in different levels.
• Client side caching can be done by changing the setting in the Webserver level . It can be OHS or Apache whatever it is being used in the project.
•  If you are using OAM (Oracle Access Manager). Then you need to change the setting of header value from no-cahce to blank. So all the settings from OHS server are applied.
• Javascript partition should be used for ADF related project.
• Minified version of CSS and JS should be placed . It reduces the content size.
• Gzip compression can be enabled in the Webserver so all the resources will be GZip compressed, But avoid GZip compression on  images.
• Activation and Passivation of the ADF Application Module should be tested under load.
• Load testing can be done using JMeter. JMeter can be integrated with ADF and Webcenter Application.
• Concept of Progressive Loading can be applied . Refer to Oracle A team blog http://www.ateam-oracle.com/improving-adf-page-rendering-time/
• Concept of deferred loading of Taskflow can also be applied. This means, the taskflow will be called when they will be needed. Otherwise all the taskflow starts rendering when the page loads. 

To be continued!!!!!!