[ 
https://issues.apache.org/jira/browse/OPENJPA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401502#comment-13401502
 ] 

Pinaki Poddar commented on OPENJPA-2220:
----------------------------------------

I think it is a good/useful feature. And I appreciate your contribution.
I would suggest to expand the scope of this idea to collect more statistics on 
field access patterns. It has been a long-held wish for many original OpenJPA 
developers to collect such detailed statistics, so that based on the access 
pattern of correlated fields we can prescribe which fetch groups will best 
serve an applications need. 

A nit: to determine whether a field is persistent, the patch code checks 
AccessCode and if the bean-method starts with "getX" etc. That check should 
include boolean fields which may start with "is". You should find the logic 
somewhere (do not remember exactly where, but around AccessCode or classes that 
use it), some code that determines whether a named field is persistent.    

                
> Persistent field fetching statistic tool
> ----------------------------------------
>
>                 Key: OPENJPA-2220
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2220
>             Project: OpenJPA
>          Issue Type: Task
>          Components: performance
>    Affects Versions: 2.3.0
>            Reporter: Helen Xu
>            Assignee: Helen Xu
>         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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to