Fibered connection pool

[k1r8r0wn]

Hello!

I'm using falcon - https://github.com/socketry/falcon in production as a app-server & the question arose whether an implemented fibered connection pool will help improve query performance, so I have several question to clearify this theme...

1. Why there is no fibered CP among this - https://github.com/jeremyevans/sequel/tree/master/lib/sequel/connection_pool ? Just to understand this in general way...
2. Maybe the extension - https://sequel.jeremyevans.net/rdoc-plugins/files/lib/sequel/extensions/fiber_concurrency_rb.html helps with this stuff, but it seems that's the not the way of actual connection pool, correct?
3. What do you think of this? - https://github.com/umbrellio/umbrellio-sequel-plugins/blob/master/lib/sequel/extensions/fibered_connection_pool.rb / https://github.com/umbrellio/umbrellio-sequel-plugins?tab=readme-ov-file#fibered-connection-pool

Much appreciated in advance!

[jeremyevans]

The fiber_concurrency extension changes the connection pool to use Fiber.current instead of Thread.current, so I would think it is exactly what you want. Is there some issue you are running into when using fibers for concurrency with the fiber_concurrency extension and Sequel's default connection pool?

The linked fibered connection pool doesn't implement some of the expected connection pool methods, and doesn't even implement a pool timeout (I guess one term to describe this would be "optimistic"). It also appears to only work correctly if all fibers accessing the pool are for the same thread (Falcon supports this, but I think it isn't the default). If you have fibers from multiple threads accessing the connection pool concurrently, it looks unsafe (e.g. @available_connections.push(connection)), at least on Ruby platforms that support native parallelism (JRuby, TruffleRuby).

[k1r8r0wn]

Thank you for the quick response, Jeremy!

Nope, I'm using this extension with Threaded connection pool, just looking for a way to improve the way it performs now...