Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 20 Aug 2015 18:59:45 +0000 (UTC)
From: "Chris Lohfink (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12857569.1440085226000.122983.1440097185987@Atlassian.JIRA>
In-Reply-To: <JIRA.12857569.1440085226000@Atlassian.JIRA>
References: <JIRA.12857569.1440085226000@Atlassian.JIRA>
 <JIRA.12857569.1440085226804@arcas>
Subject: [jira] [Commented] (CASSANDRA-10140) Enable GC logging by default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Lohfink commented on CASSANDRA-10140:
-------------------------------------------

Can we use cstar perf or something to measure the impact if any? I don't see anything but my benchmarks on laptop are inconsistent at best

> Enable GC logging by default
> ----------------------------
>
>                 Key: CASSANDRA-10140
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10140
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>         Attachments: CASSANDRA-10140.txt
>
>
> Overhead for the gc logging is very small (with cycling logs in 7+) and it provides a ton of useful information. This will open up more for C* diagnostic tools to provide feedback as well without requiring restarts.


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