Oracle JD Edwards EnterpriseOne Search- Performance Characterization Using JD Edwards EnterpriseOne Search | IT Training & Certification | Info Trek
Respect Your Dreams
Follow through on your goals with courses
Oracle JD Edwards EnterpriseOne Search- Performance Characterization Using JD Edwards EnterpriseOne Search

Following the release of EnterpriseOne Search in EnterpriseOne Tools 9.2.1.4, the Oracle JD Edwards EnterpriseOne development team initiated a project to characterize the performance of this feature with standard ‘out-of-the-box’ interactive applications and batch processes. The purpose of the performance characterization was to investigate the efficiency of various EnterpriseOne Search configurations and the impact to standard EnterpriseOne applications and batch performance when users were also running the EnterpriseOne Search feature.

The resulting performance characterization concluded:

1. EnterpriseOne Search returned a result set within seconds when the evaluation of the database query resulted in a database-indexed search. The key factors that affected how fast a database-indexed search performed are the total number of records in the primary table searched and the size of records returned in the result set. For example, a database-index search on a smaller EnterpriseOne table performed faster than a database-index search of a larger table. Similarly, on the same-sized table, a database-index search performed better when the result set returned was smaller.

2. EnterpriseOne Search performance was variable when the search was over EnterpriseOne database tables with non-indexed columns. Factors that contributed to this variability included:
a) The number of records returned in the EnterpriseOne Search result set
b) The total number of records in the EnterpriseOne database table
c) The performance of EnterpriseOne database processes based on the configuration of the EnterpriseOne Search feature and EnterpriseOne architecture

3. There was no impact to EnterpriseOne interactive and batch processes when the EnterpriseOne Searches performed well. That is to say, when the database query issued by the EnterpriseOne Search did not consume a large number of database resources, no impact to the normal day-to-day interactive and batch processes was experienced in EnterpriseOne.

4. There was an impact to performance of general interactive and batch processes when the EnterpriseOne Search database queries resulted in a database non-indexed action. There were increased database connections and increased memory utilization for the duration of the non-indexed search. The overextended use of database resources over a longer than normal time for a database request (greater than a few seconds) had a negative impact to the general EnterpriseOne user experience.

5. Proper configuration of EnterpriseOne Search Groups is a key factor in the end user experience using the EnterpriseOne Search feature. Considerations include using database indexed columns, evaluating the number of tables and views searched by an EnterpriseOne Search Group definition, and considering the complexity added by sort requests and related information selections. In short, complexity of the EnterpriseOne Search Group correlates to performance efficiency. Control over the complexity of EnterpriseOne Search is a balance between end user expectations and functionality.

Lastly, the performance of the EnterpriseOne Search feature is dependent on other factors not related to the EnterpriseOne Search feature itself, such as the EnterpriseOne architecture, specific database tuning, processor speed, memory, and network configuration. The information in this document highlights some key factors that pertain directly to EnterpriseOne Search. Due diligence by the consumer of this feature should include evaluation of the performance in their specific environments, with their EnterpriseOne architecture and database, before implementing it in a production environment for use.