Hardware acceleration for more things would be great, especially based on the success of ACCP (CASSANDRA-18624 <https://issues.apache.org/jira/browse/CASSANDRA-18624>). But I think it would be ideal to use existing compressor names and use hardware acceleration if a given JAR is present on the classpath / configured, like ACCP. Then hosts with varying hardware acceleration support can still interoperate (stream compressed SSTables between each other, for example) and migrating existing systems to use the new compressors would be as simple as ensuring a JAR is present / configured, not requiring a change to table options.
See org.apache.cassandra.security.DefaultCryptoProvider for example. > On Jan 19, 2024, at 1:51 PM, Kokoori, Shylaja <shylaja.koko...@intel.com> > wrote: > > Hi, > Latest processors have integrated hardware accelerators which can speed up > operations like compress/decompress, crypto and analytics. Here are some > links to details > 1) https://cdrdv2.intel.com/v1/dl/getContent/721858 > 2) > https://www.intel.com/content/www/us/en/content-details/780887/intel-in-memory-analytics-accelerator-intel-iaa.html > > We would like to add a new compressor which can accelerate > compress/decompress when hardware is available and which will default to > software otherwise. > > Thanks, > Shylaja
