[
https://issues.apache.org/jira/browse/CASSANDRA-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984776#action_12984776
]
Peter Schuller commented on CASSANDRA-1968:
-------------------------------------------
No, I'm saying the pause times during young-gen collections could be affected
by old-gen because the pause includes doing the promotions to old-gen.
But, this may not be an issue depending on how the free lists are managed. If
it's just "stick it in the right free list, promotion failure if it's full"
then presumably this won't be a problem. I was mostly commenting that it's not
implausible that there may be an issue that doesn't show up until after old-gen
"maturity". Not making a positive claim, just sounding caution :)
> 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.
