[
https://issues.apache.org/jira/browse/CASSANDRA-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984756#action_12984756
]
Peter Schuller commented on CASSANDRA-1968:
-------------------------------------------
I know, but promoted objects have to be put into old-gen which is free-list
based and subject to fragmentation. So on each young-gen collection you have a
latency critical spike of promotions. To the extent that those promotions is a
function of fragmentation, the pause times might be variable over time as a
function of old space.
> Increase JVM young generation size
> ----------------------------------
>
> Key: CASSANDRA-1968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1968
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 0.7.1
>
> Attachments: 1968.txt, 1968_v2.txt
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Increasing the young generation size has a profound effect on performance and
> cpu utilization. We should set it explicitly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
