-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different CLs used with different drivers #6
Comments
For example I just modified the gocql benchmark to use ONE (as the Rust one does) and I got the following results (on my laptop): ran with:
|
Oops, thanks for the information, this needs to be fixed. I thought that with replication factor equal to 1 there would be no difference no matter the consistency level. |
Ah, if you're using RF=1 then it doesn't matter. I guess we can close the issue. I'm waiting for RF=3, CL=QUORUM benchmark though. |
I used RF=1 to minimize the load on scylla and just test how fast the driver can go i'm not sure if having RF=3, CL=QUORUM would measure driver performance better |
It measures whether the driver behaves well together with the cluster. The RF=3 CL=QUORUM settings is probably the most common one in "real-life". |
Ok I opened #7 with this |
I noticed that the default CL setting in gocql is QUORUM while in scylla-rust-driver it's ONE.
Which means that you benchmarked gocql with QUORUM and scylla-rust-driver with ONE (there is no explicit changing of CL in the benchmark code).
Which means that the benchmark results are unfair.
The text was updated successfully, but these errors were encountered: