accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3761) RowEncodingIterator should take a maximum buffer size parameter
Date Wed, 29 Apr 2015 15:48:06 GMT

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

Keith Turner commented on ACCUMULO-3761:
----------------------------------------

Yeah, I think the 128 is an estimate of memory used by object overhead.  Not sure how it was
calculated for {{TransformingIterator}}.   In the past I have done experiments where I allocated
a million objects, forced gc, and then observed the memory used.  Doing this would give an
empirical estimate of object overhead.  Can not remember if this was done for {{TransformingIterator}}

> RowEncodingIterator should take a maximum buffer size parameter
> ---------------------------------------------------------------
>
>                 Key: ACCUMULO-3761
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3761
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.6.2
>            Reporter: Russ Weeks
>            Assignee: Russ Weeks
>            Priority: Minor
>              Labels: summit2015
>             Fix For: 1.7.0
>
>         Attachments: 0001-ACCUMULO-3761-RowEncodingIterator-should-take-a-maxi.patch
>
>
> It would be nice if the RowEncodingIterator and its subclasses could specify a maximum
buffer size similar to the TransformingIterator.
> Discussion [here|http://www.mail-archive.com/dev%40accumulo.apache.org/msg09821.html]



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

Mime
View raw message