geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1468) client/server messaging can create large objects
Date Fri, 03 Jun 2016 16:01:59 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314319#comment-15314319
] 

ASF subversion and git services commented on GEODE-1468:
--------------------------------------------------------

Commit 61ad7e4451aa5504c2f5d92b5d41ce1ffbcec239 in incubator-geode's branch refs/heads/develop
from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=61ad7e4 ]

GEODE-1468 client/server messaging can create large objects

After a Message has been sent we invoke clear() on each Part contained by
the Message.  This was nulling out the "part" variable of the Part objects
but if one of these "parts" was a HeapDataOutputStream it might hold a
list of large buffers.  This change set alters Part to close these
streams so that their buffers can be cleared.


> client/server messaging can create large objects
> ------------------------------------------------
>
>                 Key: GEODE-1468
>                 URL: https://issues.apache.org/jira/browse/GEODE-1468
>             Project: Geode
>          Issue Type: Bug
>          Components: serialization
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>
> Client/server messaging uses a Message object containint Parts.  Each Part holds a HeapDataOutputStream
that serializes the item placed in that Part.  Once the Message finishes transmitting its
contents it clears the "parts" array, setting it to null, but this array may consume a sizeable
amount of heap - mainly in the byte-buffer "chunks" list held in the HeapDataOutputStreams.
 It would help with GC if these "chunks" lists were cleared as part of Message clean-up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message