Avi Kivity
Avi Kivity
It was performance. I don't remember the results, it wasn't huge, but it was significant.
Does the bug have any impact? Who are the consumers?
> This series allows the users to launch a CQL-over-WebSocket server in Scylla. The server is not active by default and can be activated by setting its port in scylla.yaml,...
> > > The integration with CQL is my proprietary™ slightly hacky idea: a UNIX-domain-based socket is created and injected into our existing CQL server, and it's later used as...
> > Once activated, the server can be tested via this web interface, a static page based on javascript, and based on a typescript CQL driver: http://cqlsh.sarna.dev. If you run...
No, the client will be in your browser.
No large allocation warnings in the logs.
We have lsa detailed logging: ``` 2022-07-11T11:53:17+00:00 perf-latency-nemesis-perf-v12-db-node-b6e3deb1-1 !WARNING | scylla: [shard 5] lsa-timing - Reclamation cycle took 8000 us, trying to release 6.111 MiB preemptibly 2022-07-11T11:53:17+00:00 perf-latency-nemesis-perf-v12-db-node-b6e3deb1-1 !INFO |...
That's preemptible allocation, so it's either a huge bug in preemptible allocation, or a kernel stall.