6:50 a.m.
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Reporter: Magnus Magnus
Assignee: Manik Surtani
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:50 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Magnus Magnus updated ISPN-1141:
--------------------------------
Priority: Critical (was: Major)
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Reporter: Magnus Magnus
Assignee: Manik Surtani
Priority: Critical
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Galder Zamarreño resolved ISPN-1141.
------------------------------------
Resolution: Duplicate Issue
We're already working on an off-heap container implementation as shown in ISPN-871.
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Reporter: Magnus Magnus
Assignee: Manik Surtani
Priority: Critical
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1141:
--------------------------------
Fix Version/s: 5.1.0.Final
Affects Version/s: 5.0.0.FINAL
Priority: Major (was: Critical)
Not really a dupe of ISPN-871. ISPN-871 attempts to use a JNI-based heap in C.
Magnus' approach above is a NIO direct buffer.
Magnus, would you be interested in contributing a patch? :-)
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Magnus Magnus
Assignee: Manik Surtani
Fix For: 5.1.0.Final
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 a.m.
New subject: [JBoss JIRA] Reopened: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Manik Surtani reopened ISPN-1141:
---------------------------------
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Magnus Magnus
Assignee: Manik Surtani
Fix For: 5.1.0.Final
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-1141:
--------------------------------
Fix Version/s: 5.2.0.Final
(was: 5.1.0.Final)
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Magnus Magnus
Assignee: Manik Surtani
Fix For: 5.2.0.Final
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:47 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Magnus Magnus commented on ISPN-1141:
-------------------------------------
If think you are right the JNI based off heap container could be a better solution because
with NIO direct buffer memory free up could not handled directly.
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Magnus Magnus
Assignee: Manik Surtani
Fix For: 5.2.0.FINAL
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Johan Andries commented on ISPN-1141:
-------------------------------------
Can the DirectMemory project (https://github.com/raffaeleguidi/DirectMemory/wiki) be used
for this?
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Magnus Magnus
Assignee: Manik Surtani
Fix For: 5.2.0.FINAL
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:09 p.m.
New subject: [JBoss JIRA] (ISPN-1141) BigMemory Direct buffer
[
https://issues.jboss.org/browse/ISPN-1141?page=com.atlassian.jira.plugin....
]
Mircea Markus resolved ISPN-1141.
---------------------------------
Resolution: Done
Closed in favour of ISPN-871.
BigMemory Direct buffer
-----------------------
Key: ISPN-1141
URL: https://issues.jboss.org/browse/ISPN-1141
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Magnus Magnus
Assignee: Manik Surtani
Fix For: 5.2.0.Final
It should be configurable if data stored by NIO buffer or not.
It means data stored outside of java heap. Create, destroy in the external memory should
be managed by infinispan.
With this solution gc can run fast however infinispan node can handle huge amount of
memory.
In the current case the optional size of the java memory of a node is smaller or equals
than 4GB because of garbage collection issues above 4GB.
See a similar thing in EHCache BigMemory.
http://www.snoopal.com/documents/GaSovOTchHCsOF5X7bG691/-Scale-over-the-l...
12nd page
--
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
4234
days inactive
4718
days old
infinispan-issues@lists.jboss.org
8 comments
5 participants
participants (5)
-
Galder Zamarreño (JIRA) -
Johan Andries (JIRA)
-
Magnus Magnus (JIRA)
-
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)