Skip to main content

Improving ADF application Performance

By

Performance-issues using View Accessors and List of Values :

The default behavior of the JDeveloper and ADF has a negative effect on the performance of your application with LOV's.

For many cases we are showing some components as select one choice i.e. LOV which will be based on some VO.For that we create ViewAccessors.
ex.





Above screen shows the attribute(Descri) on which LOV is made with SomeVo.

Suppose we have to define LOV in EmployeeVO on department_id attribute.For that we have to create one DepartmentVO and EmployeeVO.
We will create 1 ViewAccessor for DepartmentVO based on department id in EmployeeVO.
If you drag this EmployeeVO on your page you can see that executeQueryForCollection is called only once for EmployeeVO but for multiple times it is called for DepartmentVO.

The query to determine the choice-list values for the DepartmentId is executed for every row in the EmployeeView.
This is unnecessary and can have the performance impact of your application.


The behavior is caused by a property of the view accessor that is 'Row Level Bind Values'.
As show below.
                                                                                 


This can have a negative impact on the number of queries executed, and the performance of your application.
Default this property value is blank and you can give values from (true or false).blank value is nothing but "true".
For performance isue set this value explicitly to 'false' if you have no bind variables that really depend on some attribute values in the row. 
Conclusion : For ViewAccesssor  setting 'Row Level Bind Values' to "false" increases your application performance.



Comments

Post a Comment

Popular posts from this blog

Oracle ADF Interview questions

By
Why ADF ?     Oracle ADF (Application Development Framework) is state of the art technology to rapidly build enterprise application. ADF is a mature J2EE development framework and many other products under Oracle Fusion Middleware stack are build upon ADF 11g. ADF provides variety of inbuilt components that minimizes the need to write code allowing users to focus more on features and business aspects of the application. With WebCenter and SOA plugins, we can also integrate WebCenter Services and SOA into your application making it rich and extensible. Explain about JSF lifecycle ? The six phases of the JSF application lifecycle are as follows (note the event processing at each phase): -Restore view -Apply request values; process events -Process validations; process events -Update model values; process events -Invoke application; process events -Render response Immediate=true : A command button that does not provide ...
6 comments
Read more

The file store "WLS_DIAGNOSTICS" could not be opened

By
WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon
1 comment
Read more

Overview Editor for bc4j.xcfg

By
This is used to customize the configuration settings for the application pool, connection pool, and transactions. Select the Application Module, then select a configuration from the Configurations list. You can specify a Default Configuration from the dropdown to use with selected application module. Edit the name of the configuration in Details. Its having 3 tabs 1.Database and Scalability 2. Properties 3. Custom Properties Database and Scalability Tab : In Database and Scalability you can mention the JDBC data source definition for each application module. You can choose to connect to a JDBC data source or to a JDBC URL.The default connection type is the default data source. A data source is a vendor-independent encapsulation of a database server connection on the application server. 1. Data sources ( JNDI name) offer advantages over a JDBC URL connection because the data source can be tuned, reconfigured, or remapped without changing the deployed application. 2. JDB...
4 comments
Read more