[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-485) Refactor the current Collection classes (list and set)

[Elias Ross (JIRA)]

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

Elias Ross updated JBCACHE-485:
-------------------------------

    Attachment: icache.diff

For the List, adding an IntegerCache might help performance with List operations slightly. Again, using Integer.valueOf(int i) would be better than strings, but if there's that restriction, it's much better to use pooled Strings. I haven't looked into this.

> Refactor the current Collection classes (list and set)
> ------------------------------------------------------
>
>                 Key: JBCACHE-485
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-485
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: PojoCache
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>            Priority: Critical
>             Fix For: PojoCache
>
>         Attachments: icache.diff, set.diff
>
>   Original Estimate: 4 weeks
>  Remaining Estimate: 4 weeks
>
> Current implementation of Collection uses direct coupling to the cache store indices. E.g., we map them into subtree according to index ordering. This is not very desirable for performance reason. We should consider to provide a indirect mapping such that it is considered a graph instead of ordered tree.
> Or we should investigate whether it is possible to use a proxy operates on java.util.* classes such that we don't need to have our own implementation. The JDK lincense aside, ArrayList, e.g., uses an internal transient array. Is it possible to "aspectize" on that array only?

-- 
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