Interest in supporting a connection pool?

[Chris]

Hi,
I spent some time looking into Celluloid (https://github.com/celluloid/
celluloid) and thinking about how I could integrate it into my current
app which uses Ohm. When I first added Celluloid to my models, I
realized that for every Ohm action, it was making a new connection and
saw that soon redis was overwhelmed :)

Using an existing connection pool gem (https://github.com/mperham/
connection_pool), I was able to string a few things together so at
least the basic object creation could work in Ohm using a redis
connection pool. Here's what I have so far:
https://github.com/compressed/ohm/commits/connection_pool (last two
commits show everything).

Is there any interest in something like this? I could try my hand at
validating the rest of the actions as well and maybe abstracting this
into some sort of optional configuration setting. If others want to
pitch in, have done something similar, or have comments, I'm all ears!

Thanks,
Chris

[David Badley]

I had this issue as well when I was using Ohm.  Recognized it because at scale it was bottlenecking on CPU time.  Wasn't sure why, but this explains it perfectly.