openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2220) Persistent field fetching statistic tool
Date Tue, 03 Jul 2012 18:31:20 GMT


Rick Curtis commented on OPENJPA-2220:

I committed revision 1356860 to trunk.

This first iteration of this tool is limited in usage. Currently it is not configurable. Once
it is on the classpath, it starts running. When you take it off the classpath, it stops running.
It is also depended upon runtime (ie: javaagent or container enhancement) enhancement.

I modified a number of things from the original patch to make it more usable... When the code
first gets loaded up you'll see this message[1] so a user is notified when it is running.
Also, when the statistics are dumped you'll see a message along these lines[2].

I'll also note that I modified the pom to spit out another jar file that allows this tool
to work in a WebSphere environment. 

[1] 3094  fetchStatisticPU  INFO   [main] openjpa.Runtime - The FetchStatisticsAuxEnhancer
has been loaded and is tracking persistent field usage.
[2] 4226  fetchStatisticPU  INFO   [Thread-5] openjpa.Runtime - Successfully collected fetch
statistics from Entities [org.apache.openjpa.enhance.stats.AEntity,...,  org.apache.openjpa.enhance.stats.EEntity].
The following fields are FetchType.EAGER and were never fetched [ total 10 ] : 
> Persistent field fetching statistic tool
> ----------------------------------------
>                 Key: OPENJPA-2220
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: tooling
>    Affects Versions: 2.3.0, 2.2.1
>            Reporter: Helen Xu
>            Assignee: Rick Curtis
>         Attachments: OPENJPA-2220Patch.txt, statisticToolDocPatch.txt
> This task is to create a statistic tool which monitors the persistent fields fetching
and finds out the fields which are never accessed. Based on the statistic data, user can set
the field access type to LAZY to improve the performance by eliminating the data loading and
processing time.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message