[infinispan-issues] [JBoss JIRA] (ISPN-871) Out-of-heap data container implementation

[Manik Surtani (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-871:
-------------------------------

    Fix Version/s: 5.2.0.Beta1
                       (was: 5.2.0.Alpha4)
      Description: 
The {{DataContainer}} interface could be implemented using a off-heap impl in C, using a wrapper around [TBB|http://threadingbuildingblocks.org/]'s concurrent hashmap.

Cheap and easy way, no memory management needed, at worst case same performance as the Java CHM-like impl of the data container + some JNI overhead.  Potential benefit of large data heaps.

  was:The DataContainer interface could be implemented using a off-heap impl in C, using mmap.  It would require custom memory management (gc-lite?) to reclaim free space, as well as reimplementing of eviction algorithms to maintain the contract of a self-sizing data container, but the benefits of this would be the ability to address very large amounts of memory with minimal gc overhead from the JVM.

       Complexity: Medium  (was: High)

    
> Out-of-heap data container implementation
> -----------------------------------------
>
>                 Key: ISPN-871
>                 URL: https://issues.jboss.org/browse/ISPN-871
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration
>            Reporter: Manik Surtani
>            Assignee: Tristan Tarrant
>              Labels: gc, jni, native, performance, research
>             Fix For: 5.2.0.Beta1, 5.2.0.Final
>
>
> The {{DataContainer}} interface could be implemented using a off-heap impl in C, using a wrapper around [TBB|http://threadingbuildingblocks.org/]'s concurrent hashmap.
> Cheap and easy way, no memory management needed, at worst case same performance as the Java CHM-like impl of the data container + some JNI overhead.  Potential benefit of large data heaps.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira