[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-584) Investigate use of lazy mapping for PojoCache

[Jason T. Greene (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-584?page=all ]

Jason T. Greene updated JBCACHE-584:
------------------------------------

    Assignee: Jason T. Greene  (was: Ben Wang)

> Investigate use of lazy mapping for PojoCache
> ---------------------------------------------
>
>                 Key: JBCACHE-584
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-584
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Ben Wang
>         Assigned To: Jason T. Greene
>             Fix For: PojoCache 2.1.0
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Recent perf test on PojoCache shows bottleneck is on the initial mapping of putObject causing numerous trips to the local cache store. To optimize it further, either the TreeCache local mode need to be enhanced. Or one solution to this is the use of lazy mapping of the pojo. For example, when putObject is called, pojo is not mapped. Instead, it is stored under a "Serialized" state (can use JBossSerialization if  pojo is not even Seriailizable) first. Then when the field is modified (detected from the CacheInterceptor), we will then map it lazily to the PojoCache store.
> The performance gain can be had, if 1) initial saving of mapping, 2) field update is only selected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira