You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Saurabh Seth (JIRA)" <ji...@apache.org> on 2016/08/11 09:12:20 UTC

[jira] [Commented] (PHOENIX-541) Make mutable batch size bytes-based instead of row-based

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

Saurabh Seth commented on PHOENIX-541:
--------------------------------------

If no one has started working on this maybe I can take this up.

I have a question though. What is the plan for the phoenix.mutate.batchSize and phoenix.mutate.maxSize configuration variables that are exposed to end users? How do we want to deal with this for upgrades?

> Make mutable batch size bytes-based instead of row-based
> --------------------------------------------------------
>
>                 Key: PHOENIX-541
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-541
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 3.0-Release
>            Reporter: mujtaba
>              Labels: newbie
>
> With current configuration of row-count based mutable batch size, ideal value for batch size is around 800 rather then current 15k when creating indexes based on memory consumption, CPU and GC (data size: key: ~60 bytes, 14 integer column in separate CFs)



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