[
https://issues.apache.org/jira/browse/PHOENIX-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706038#comment-15706038
]
James Taylor commented on PHOENIX-541:
--------------------------------------
Along with making the batch size byte-based, we need to also make the max
commit size byte based (phoenix.mutate.maxSize). We should substantially lower
the default value as well.
We can do this in a backward compatible manner by deprecating
phoenix.mutate.maxSize and phoenix.mutate.batchSize and then creating new
config parameters phoenix.mutate.batchSizeBytes and
phoenix.mutate.maxSizeBytes. When we look for the limit in our code, we can
give preference to the byte-based config parameters first.
> 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
> Fix For: 4.10.0
>
>
> 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)
