we are seeing similar perf issues with counter writes - to reproduce:
cassandra-stress counter_write n=10 no-warmup cl=LOCAL_QUORUM -rate
threads=50 -mode native cql3 user= password= -name
op rate: 39,260 ops (4.1) and 63,689 ops (4.0)
latency 99th percentile: 7.7ms (4.1) and 1.8ms (4.0)
> For your #1 - if there are going to be 100+ million vectors, wouldn't I
want the search to go across nodes?
If you have a replication factor of 3 and 3 nodes, every node will have a
complete copy of the data, so you'd only need to talk to one node. If your
replication factor is 1, you'd have to
Thank you all for the details on this.
For your #1 - if there are going to be 100+ million vectors, wouldn't I
want the search to go across nodes?
Right now, we're running both weaviate (8 node cluster), our main
cassandra 4 cluster (12 nodes), and a test 3 node cassandra 5 cluster.
Weaviate
Hello to all users, contributors and Committers!
[ You are receiving this email as a subscriber to one or more ASF project
dev or user
mailing lists and is not being sent to you directly. It is important that
we reach all of our
users and contributors/committers so that they may get a chance t
Hi All,
Was going through this mail chain
(https://www.mail-archive.com/user@cassandra.apache.org/msg63564.html)
and was wondering that if this could cause a performance degradation in
4.1 without changing compactionThroughput.
As seeing performance dip in Read/Write after upgrading from 4.0 to
