This was requested before, it's a reasonable request, but I consider it low priority. Why? For a few reasons -- one, you cannot write at high rates to rqlite due to the nature of Raft. You will be limited by disk IO long before you hit network limits writing over localhost.

Reading is different, you can read at a high rate from rqlite, especially if you use None Read consistency. But that means that this feature would only benefit reads. This reduces the potential impact of this feature.

Reading is different, you can read at a high rate from rqlite, especially if you use None Read consistency. But that means that this feature would only benefit reads. This reduces the potential impact of this feature.

Yes this was mainly proposed for read only. It has benefits on distributed implementations. Pls don't burry it and keep in the backlog, if you can.