Hi Alex, If the changes are small and localized, then I don't see a big problem. I can help with the review as a second reviewer if needed, to satisfy the requirement of having two committers involved. In any case, I'm trying to keep an eye on all performance-related changes in the codebase. Regards, Dmitry
On Wed, 8 Jul 2026 at 13:59, Alex Petrov <[email protected]> wrote: > Hey folks, > > A friend of mine is building Perfloop [1]; the way they describe it, > "closed loop performance engineering". They already have several upstream > OSS merges, including two in parquet-go [2] and one in > RoaringBitmap/roaring [3], all benchmark-verified. > > I was curious if they can find anything in Cassandra, so asked them to try > it against our repo, and they've found a bunch of performance improvements, > many of which seem to be quite easy to review and verify. All of them come > with a finding, benchmark, a patch, and verification of an improvement, > which is pretty useful for a reviewer. > > I've looked over the issues, and will be reviewing and committing some of > them. Is there anything that prevents us from committing the patches that > were fully LLM-authored, assuming contents are solid? > > --Alex > > [1] https://perfloop.ai/ > [2] https://github.com/parquet-go/parquet-go/pull/550 > [3] https://github.com/RoaringBitmap/roaring/pull/532 > -- Dmitry Konstantinov
