[infinispan-issues] [JBoss JIRA] (ISPN-7802) Use chunked read in TcpTransport

Radim Vansa (JIRA) issues at jboss.org
Mon May 15 04:33:00 EDT 2017


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

Radim Vansa updated ISPN-7802:
------------------------------
    Description: 
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.

EDIT: As Tristan pointed out, the {{BufferedInputStream}} does not grow in our use case, but 

  was: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.



> Use chunked read 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.
> EDIT: As Tristan pointed out, the {{BufferedInputStream}} does not grow in our use case, but 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the infinispan-issues mailing list