Performance needs to be ingrained in your application – it cannot be added in during the last stages of development. In this video I discuss how you can optimize the performance of your Oracle ADF Fusion application, diagnose and solve typical performance problems, and build an efficient, responsive, scalable ADF application that circumvents common bad practices. This video was originally presented as part of the Oracle ACE Track during the Oracle Technology Network Virtual Developer Day event “Oracle ADF Development – Web, Mobile and Beyond.” Last week the video was published on OTNArchBeat (Oracle Architect Community Video Channel).
Video session of Oracle Virtual Developer Day (42 minutes)
Important: to watch in high quality, select HD quality (720p).
In the video I discuss several categories of things that are happening frequently too slowly, too often, too little, too soon and too big in ADF applications, and solutions.
Agenda of video session – things that are happening in ADF applications:
- Too slowly (too slow ViewObject queries, EntitObject DML operations, ApplicationModule pooling passivations and activations)
- Too often (too many (mini) queries, too many database round-trips, too many HTTP Requests, too many full HTTP Requests, too frequent ApplicationModule passivation & activation, unintentionally left iterators in PageDefs)
- Too big (too much data in ADF BC memory, too big scope for managed beans, too much HTML to the browser, too much logging on)
- Too soon (too soon executed taskflows, too soon instantiated ApplicationModules, ADF UI components that are loaded too soon (Immediate versus lazy))
- Too little (too little Caching, too little JVM Heap size)
At AMIS we frequently use the ADF Performance Monitor to detect, analyze and help resolve the problems discussed in this video.
The PPT version of the video is available here (contains a lot of animations).