Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7CB6B181DF for ; Sun, 30 Aug 2015 05:44:46 +0000 (UTC) Received: (qmail 14485 invoked by uid 500); 30 Aug 2015 05:44:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 14450 invoked by uid 500); 30 Aug 2015 05:44:46 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 14436 invoked by uid 99); 30 Aug 2015 05:44:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Aug 2015 05:44:46 +0000 Date: Sun, 30 Aug 2015 05:44:46 +0000 (UTC) From: "sankalp kohli (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8929) Workload sampling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721400#comment-14721400 ] sankalp kohli commented on CASSANDRA-8929: ------------------------------------------ We are also looking at doing something very similar so this feature will be of great help. It will be a good start to to record the traffic but we should also try to find a way to find something about the existing data. A simple select statement on a small CQL partition will be very different from the one on large CQL partition in terms of load on C*. We should try to find a way to deal with this as well ideally.... may be as a different JIRA. (I am not sure if someone also mentioned this before in the comments) > Workload sampling > ----------------- > > Key: CASSANDRA-8929 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8929 > Project: Cassandra > Issue Type: New Feature > Components: Tools > Reporter: Jonathan Ellis > Assignee: Robert Stupp > > Workload *recording* looks to be unworkable (CASSANDRA-6572). We could build something almost as useful by sampling the requests sent to a node and building a synthetic workload with the same characteristics using the same (or anonymized) schema. -- This message was sent by Atlassian JIRA (v6.3.4#6332)