Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <24511085.19291272577133850.JavaMail.jira@thor>
Date: Thu, 29 Apr 2010 17:38:53 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1035) Implement User/Keyspace
 throughput Scheduler
In-Reply-To: <17623898.8461272561235266.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-1035:
-------------------------------------------

of course that assumes each app is doing the same amount of work per SP call, which is dubious in the presence of mutliget + batch_mutate.

> Implement User/Keyspace throughput Scheduler
> --------------------------------------------
>
>                 Key: CASSANDRA-1035
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1035
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>
> To support multiple applications on top of a single Cassandra cluster (and to protect against badly behaving clients) having a very simple scheduler for MUTATION-STAGE and READ-STAGE would be very beneficial.
> Since all tasks are short lived, a sufficient scheduler would probably only need to manage the queue of incoming requests, and weight them based on an assigned ID. The ID could be dynamically determined by using ip, userid or keyspace for instance, and then each Runnable would be assigned an ID.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.