[JBoss JIRA] (ISPN-7803) Functional commands-based AtomicMap
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-7803?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-7803:
------------------------------
Labels: atomic_map (was: )
> Functional commands-based AtomicMap
> -----------------------------------
>
> Key: ISPN-7803
> URL: https://issues.jboss.org/browse/ISPN-7803
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Labels: atomic_map
>
> Implement AtomicMap based on the functional commands instead of DeltaAware.
> * Fine-grained and coarse-grained locking options should be preserved, though it might be necessary to introduce further locking to achieve atomicity during command execution.
> * Support transactional caches.
> * This implementation should replace the original implementation (temporarily allowing to opt-in for the old variant with a system property).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (ISPN-7802) Use non-growing buffered input stream in TcpTransport
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7802?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant edited comment on ISPN-7802 at 5/5/17 8:50 AM:
---------------------------------------------------------------
This might not be necessary if mark isn't used (and it doesn't look like it).
was (Author: nadirx):
This might not be necessary if mark isn't use (and it doesn't look like it).
> Use non-growing buffered input stream in TcpTransport
> -----------------------------------------------------
>
> Key: ISPN-7802
> URL: https://issues.jboss.org/browse/ISPN-7802
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: Tristan Tarrant
>
> The buffering implementation of {{TcpTransport.socketInputStream}} needs to use fixed size input buffer, rather than growing as {{BufferedInputStream}} does. Growing buffer can lead to excessive memory consumption on heap, and more importantly, by direct memory allocated in JDK classes and pooled in thread-local caches.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (ISPN-7805) Use non-growing buffered input stream in TcpTransport
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-7805:
--------------------------------------
Summary: Use non-growing buffered input stream in TcpTransport
Key: ISPN-7805
URL: https://issues.jboss.org/browse/ISPN-7805
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 9.0.0.Final
Reporter: Wolf-Dieter Fink
Assignee: Tristan Tarrant
The buffering implementation of {{TcpTransport.socketInputStream}} needs to use fixed size input buffer, rather than growing as {{BufferedInputStream}} does. Growing buffer can lead to excessive memory consumption on heap, and more importantly, by direct memory allocated in JDK classes and pooled in thread-local caches.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (ISPN-7804) Use non-growing buffered input stream in TcpTransport
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created ISPN-7804:
--------------------------------------
Summary: Use non-growing buffered input stream in TcpTransport
Key: ISPN-7804
URL: https://issues.jboss.org/browse/ISPN-7804
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 9.0.0.Final
Reporter: Wolf-Dieter Fink
Assignee: Tristan Tarrant
The buffering implementation of {{TcpTransport.socketInputStream}} needs to use fixed size input buffer, rather than growing as {{BufferedInputStream}} does. Growing buffer can lead to excessive memory consumption on heap, and more importantly, by direct memory allocated in JDK classes and pooled in thread-local caches.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months