Skip to main content

ADF : Performance Tuning


I am going through a set of performance tuning exercises and so here is my plan and set of items I will address. I hope to post results for each of these steps once I have completed them. 
1)     Build
a.     Ant (Auditing only run for CI builds)
Ojdeploy64 - 45,41,42,42 seconds
Ojdeploy - 41,40,40,39 seconds
Negligible difference but non 64 bit seems a little bit faster (non scientific one project test)
b.    Maven - my maven build tests where about 10 seconds quicker than the ojdeploy builds but this is exculding the generation of some of the custom adf files.
2)     Jdeveloper
a.     Memory
AddVMOption  -Xmx1536M
AddVMOption  -Xms512M
b.    Garbage collection
AddVMOption -XX:+AggressiveOpts
AddVMOption -XX:+UseStringCache
AddVMOption -XX:+OptimizeStringConcat
AddVMOption -XX:+UseCompressedStrings
AddVMOption -XX:+ScavengeBeforeFullGC
AddVMOption -XX:+UseConcMarkSweepGC
AddVMOption -XX:+UseGCOverheadLimit
AddVMOption -XX:+UseCompressedOops
c.     64 bit
Install jdev with 64 bit VM.
The results for this are a bit subjective but jdev runs out of memory less and feels a bit more snappy.
3)     Weblogic
b.    Memory, JVM (jrockit)
c.     Cache
d.    Data Source
e.     Production Mode
4)     OraformsFaces performance
a.     Disable logging
b.    com.commit_consulting.oraformsfaces.UNIQUE_APPLET_PER_SESSION
c.     Forms server
5)     AM
a.     Pooling and settings
b.    Nested and shared AM’s
6)     VO
a.     Tuning parameters
b.    Read/Insert only VO’s
c.     Bind variables
d.    In memory filtering
7)     EO
a.     Batch processing
b.    Associations
8)     Logging
9)     OCI Drivers
10)  JSF
a.     Caching static stuff
b.    Templates
c.     Web.xml, Trinidad-config etc settings
d.    Compression
e.     Page Load times
I have purposefully left off any performance tuning of the DB that we have done (indexes, partitioning, etc) because there is a huge body of knowledge for this stuff and I am mainly interested in the ADF side.
References:

Comments

  1. Thanks for consolidating all on to a single place

    -Satyendra

    ReplyDelete

Post a Comment

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be found. If omitted, the Profile is assumed to be in the Workspace.   -buildfile            full path to a build file for batch deploy   -buildfileschema  print XML Schema for the build file