Hello,
On Wed, Dec 14, 2016 at 10:25 PM, <
pjs...@gmail.com> wrote:
> Before doing a real benchmark on our company's servers, I tried to do a
> simple test by installing Centos 7.0 on my laptop.
> cassandra-stress with Cassandra reported 54000 ops/sec while with Scylla
> only 24000 op/s.
> Cassandra could handle more than hundred threads while with Scylla timeouts
> started much earlier.
>
> Is this because there's no network, partitioning overhead?
There are two things at play here: (1) Scylla is very sensitive to
other threads stealing the CPU's it is running its reactor loop on and
(2) Scylla takes over _all CPUs_ by default. So as you start the
"cassandra-stress" process on the same machine, you'll have less CPU
resources to run it and Scylla's performance is hurt because of CPU
sharing.
I don't really recommend running either Scylla or Cassandra and the
load generator on the same machine. But if you insist on doing that,
you probably should limit the number of CPUs Scylla is using with the
"--smp" command line argument.
- Pekka