Is there something I can do to speed up the deserialisation ?
In this example I did a count query, but in reality I need the actual data.
Write pattern in this table is such that all data for a given row is
written at the same time, so I know I can use frozen udt instead of this,
making it
On 4/11/23 19:53, Bowen Song via user wrote:
That error message sounds like one of the nodes timed out in the paxos
propose stage. You can check the system.log and gc.log and see if you
can find anything unusual in them, such as network errors, out of sync
clocks or long stop-the-world GC
Reading 4MB from 70k rows and 13 columns (0.91 million cells) from disk
in 120ms doesn't sound bad. That's a lots of deserialisation to do. If
you want it to be faster, you can store the number of rows elsewhere if
that's the only thing you need.
On 11/04/2023 07:13, Gil Ganz wrote:
Hey
I
That error message sounds like one of the nodes timed out in the paxos
propose stage. You can check the system.log and gc.log and see if you
can find anything unusual in them, such as network errors, out of sync
clocks or long stop-the-world GC pauses.
BTW, since you said you want it to be
Hi folks!
Ralph here from the Samba team.
I'm currently doing research into Opensource distributed NoSQL key/value
stores to be used by Samba as an more scalable alternative to Samba's
own homegrown distributed key/value store called "ctdb" [1].
As an Opensource implementation of the SMB
Hey
I have a 4.0.4 cluster, with reads of partitions that are a bit on the
bigger side, taking longer than I would expect.
Reading entire partition that has ~7 rows, total partition size of 4mb,
takes 120ms, I would expect it to take less.
This is after major compaction, so there is only one
