[jira] Updated: (OPENJPA-407) Cache SQL (or closer precursors to SQL) more aggressively

["Patrick Linskey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey updated OPENJPA-407:
------------------------------------

    Attachment: OPENJPA-407.patch

This patch seems like it addresses some of the right areas to make improvements on this issue, at least for lookups by id (find() and lazy-loads). It builds a cache of Select instances keyed off of relevant data, and uses this cache in JDBCStoreManager to avoid recreating Select records.

However, initial testing seems to indicate that there's actually a performance loss. Additionally, all the OpenJPA tests are passing, but a small number of the TCK tests fail with this change.

> Cache SQL (or closer precursors to SQL) more aggressively
> ---------------------------------------------------------
>
>                 Key: OPENJPA-407
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-407
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc, kernel, query, sql
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0
>            Reporter: Patrick Linskey
>             Fix For: 1.1.0
>
>         Attachments: OPENJPA-407.patch
>
>
> When data is not available in the data cache, OpenJPA dynamically creates SQL to look up the requested data. OpenJPA should more aggressively cache this SQL to accelerate pathways from a cache miss to the database.
> The generated SQL takes a number of factors into account, including the requested records, transaction status, currently-loaded data, and the current fetch configuration. Any caching would need to account for these factors as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.