[OPENJPA-703] Cache ResultObjectProvider data to improve query performance

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M2
• Fix Version/s: 2.0.0-M3
• Component/s: kernel
• Assignee: Pinaki Poddar
• Reporter: Ron Pressler
• Created: 25/Aug/08 17:08
• Updated: 07/Feb/12 19:18
• Resolved: 27/Aug/09 16:58

Description

Profiling indicated that JDBCStoreQuery.populateSelect consumes a significant amount of CPU, and is executed every time a query is run. While, in fact, the actual PreparedStatement is created and run only in QueryImpl.toResult. It seems like the returned ResultObjectProvider from JDBCStoreQuery.executeQuery can be at least partially cached, or even cached in its entirety (provided care is taken with the context parameters).
It seems like such an improvement would significantly improve query performance.

Issue Links

• is related to: OPENJPA-886 Certain query failing after svn:739123
• is related to: OPENJPA-924 Cache Finder Query for performance enhancement
• relates to: OPENJPA-2121 Determine proper configuration of SQL caches
• relates to: OPENJPA-2099 Reuse relationship selection
• relates to: OPENJPA-407 Cache SQL (or closer precursors to SQL) more aggressively