[jira] [Commented] (ACCUMULO-3246) More insight into native map utilization/usage

["Eric Newton (JIRA)" <ji...@apache.org>]

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

Eric Newton commented on ACCUMULO-3246:
---------------------------------------

We do have *some* understanding.  For example, increasing the size of the in-memory map 2x does not double ingest performance.  In fact, it's surprising how little it impacts ingest.

You want something big enough to make a big chunk for compression/hdfs performance for each tablet.  Anything beyond that doesn't seem to help that much.

> More insight into native map utilization/usage
> ----------------------------------------------
>
>                 Key: ACCUMULO-3246
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3246
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Josh Elser
>             Fix For: 1.7.0
>
>
> I often find that I choose a value for the size of the native map out of the air without really having a good understanding of why I chose it  (aside from considerations of table.compaction.minor.logs.threshold and tserver.walog.max.size).
> We don't have any insight into some basic metrics on the native maps. It would be nice to be able to answer questions like
> * What is the utilization (space) of the native maps for a server
> * How much time is the server spending writing data as opposed to allocating new blocks
> I'm sure there are some other questions too.



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