the
capability pluggable for now. We will modify the code and come back with the
changes in a few weeks.
Thank you,
Shylaja
From: C. Scott Andreas
Sent: Monday, June 09, 2025 8:51 PM
To: dev@cassandra.apache.org
Cc: dev@cassandra.apache.org
Subject: Re: [DISCUSS] CEP-49: Hardware-accelerated c
the performance
gains. Intel® QuickAssist Technology - Deliver Compression Efficiencies in the Cloud with Intel® QAT and QATzip Solution Brief Thank
you, Shylaja From: Jeff Jirsa Sent: Thursday, June 05, 2025 12:13 PM To: dev@cassandra.apache.org Cc:
dev@cassandra.apache.org Subject: Re: [DIS
If it is a plug-in solution, I might think it is a good idea. What
Cassandra needs to do is to define the interface (may be based on the need
for hardware acceleration). It is not a good idea to add hardware-dependent
classes to the Cassandra code.
Abe Ratnofsky 于2025年6月6日周五 06:08写道：
> I’m als
I’m also supportive of making this behavior pluggable, and starting with an
out-of-tree implementation.
I do think we need to extend ICompressor to differentiate between compression
format and implementation to make this work nicely. A new QatZstdCompressor
should be read and write compatible w
>
> Living in the repo - how would we even run CI? How can the PMC vote to
> release code they can’t execute?
>
This would be a concern for me as well.
On the pluggable front, the compaction compression class is already a
pluggable interface. Is it worth having a second interface for the
accelera
Pluggable is a net winLiving in the repo - how would we even run CI? How can the PMC vote to release code they can’t execute? On Jun 5, 2025, at 12:37 PM, Josh McKenzie wrote:From skimming the CEP (limited on time):We propose a framework which can perform the offload when hardware is available an
>From skimming the CEP (limited on time):
> We propose a framework which can perform the offload when hardware is
> available and will default to software otherwise. The framework also allows
> for additional accelerators in the future.
I'm provisionally receptive to this. Not sure whether we'd
One perpetual challenge with customizing codebase for dedicated hardware is ongoing support / testing / maintenance followed by ensuring vendor agnostic / neutral accessQAT is one of those things that’s great for a set of people paying for it, but I don’t know any current contributors who have acc
