[
https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243924#comment-14243924
]
Benedict commented on CASSANDRA-8457:
-------------------------------------
bq. cstar doesn't support multiple stress clients
Stress could be modified to support simulating true multiple client access;
i've filed CASSANDRA-8466.
What we really need is to be able to fire up a (much) larger cluster, though.
With our current hardware probably necessitating multiple VMs per node - say,
4, giving a viable cluster of 24 which is probably about bare minimum for these
kinds of tests. This necessarily pollutes the results somewhat since each VM
will have only half a CPU, and incur extra thread signalling penalties, but
it's better than nothing. Either that or we get a bunch of cheapo nodes, or we
add EC2 integration.
[~enigmacurry] any plans in the works to introduce support for large clusters?
> nio MessagingService
> --------------------
>
> Key: CASSANDRA-8457
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8457
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Ariel Weisberg
> Labels: performance
> Fix For: 3.0
>
>
> Thread-per-peer (actually two each incoming and outbound) is a big
> contributor to context switching, especially for larger clusters. Let's look
> at switching to nio, possibly via Netty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
