Lucas Kent

as of https://github.com/shotover/shotover-proxy/pull/1555 we no longer keep outgoing connections open after processing a `use` statement. It would be ideal if we could reintroduce that functionality in the future.

Checking the upstreamed nextest fix still works for us.

Improve performance of writing to sink outgoing connections

5

From looking at a profiler we spend significantly more time writing to the sink socket to the DB than we do writing to the source socket going to the client....

testing if this fixes https://github.com/shotover/shotover-proxy/issues/1533

cassandra protocol v5: replace slow crc implementation

1

crc24 is very slow and crc32 implementation should be benchmarked against https://github.com/zowens/crc32c

~~ec2-cargo should handle sigint by cancelling in progress command and waiting for another prompt.~~ I spent some time using ec2-cargo today, I think I've taken the wrong approach with it....

Port redis pubsub tests to fred

1

In order to update the redis dependency used by our test suite we will need to migrate the pubsub tests to use a different redis client. This is because the...

https://github.com/shotover/shotover-proxy/pull/1476 kicked off a bunch of work to refactor shotover in order to achieve its full performance potential. I had a plan for future work but it was mostly in...

I run: ```shell ./aws-windsock-kafka.sh cloud-setup "name=kafka shotover=standard" ./aws-windsock-kafka.sh cloud-run --bench-length-seconds 60 "name=kafka shotover=standard" ``` The issue occurs when the bench run reaches `name=kafka,shotover=standard,size=1B,topology=cluster1`:  All throughput stops and then the...

Currently shotover supports some runtime configuration via a built in webserver. We currently have 1 webserver for general overall configuration and a separate webserver for tee transform configuration. But this...