I am just learning the ropes here so perhaps it is not CEP worthy. That
being said, It felt like there was a lot of information to put into and
track in a ticket, particularly when I expected discussion about how to
best encode, changes to the algorithms etc. It feels like it would be
difficult to track. But if that is standard for this project I will move
the information there.
As to the benchmarking, I had thought that usage and performance
measures should be included. Thank you for calling out the subset of
data selected query as being of particular importance.
Claude
On 06/09/2022 03:11, Abe Ratnofsky wrote:
Looking at this link:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-23%3A++Enhancement+for+Sparse+Data+Serialization
Do you have any plans to include benchmarks in your test plan? It would be
useful to include disk usage / read performance / write performance comparisons
with the new encodings, particularly for sparse collections where a subset of
data is selected out of a collection.
I do wonder whether this is CEP-worthy. The CEP says that the changes will not
impact existing users, will be backwards compatible, and overall is an
efficiency improvement. The CEP guidelines say a CEP is encouraged “for
significant user-facing or changes that cut across multiple subsystems”. Any
reason why a Jira isn’t sufficient?
Abe
On Sep 5, 2022, at 1:57 AM, Claude Warren via dev <dev@cassandra.apache.org>
wrote:
I have just posted a CEP covering an Enhancement for Sparse Data Serialzation.
This is in response to CASSANDRA-8959
I look forward to responses.
