1
0
Fork 0
mirror of https://github.com/mperham/connection_pool synced 2023-03-27 23:22:21 -04:00
connection_pool/README.md

107 lines
2.9 KiB
Markdown
Raw Normal View History

2014-03-13 23:31:25 -04:00
connection\_pool
2014-03-13 21:44:54 -04:00
=================
2015-01-18 14:54:59 -05:00
[![Build Status](https://travis-ci.org/mperham/connection_pool.svg)](https://travis-ci.org/mperham/connection_pool)
2011-05-14 18:36:17 -04:00
Generic connection pooling for Ruby.
2014-03-13 21:44:54 -04:00
MongoDB has its own connection pool. ActiveRecord has its own connection pool.
This is a generic connection pool that can be used with anything, e.g. Redis,
Dalli and other Ruby network clients.
2011-05-14 18:36:17 -04:00
2011-05-14 18:36:17 -04:00
Usage
2014-03-13 21:44:54 -04:00
-----
2011-05-14 18:36:17 -04:00
2014-03-13 21:44:54 -04:00
Create a pool of objects to share amongst the fibers or threads in your Ruby
application:
2011-05-14 18:36:17 -04:00
``` ruby
$memcached = ConnectionPool.new(size: 5, timeout: 5) { Dalli::Client.new }
```
2011-05-14 18:36:17 -04:00
Then use the pool in your application:
``` ruby
$memcached.with do |conn|
conn.get('some-count')
end
```
2011-05-14 18:36:17 -04:00
If all the objects in the connection pool are in use, `with` will block
until one becomes available. If no object is available within `:timeout` seconds,
`with` will raise a `Timeout::Error`.
2013-09-24 12:37:58 -04:00
Optionally, you can specify a timeout override using the with-block semantics:
``` ruby
$memcached.with(timeout: 2.0) do |conn|
conn.get('some-count')
2013-09-24 12:37:58 -04:00
end
```
2014-03-13 21:44:54 -04:00
This will only modify the resource-get timeout for this particular
invocation. This is useful if you want to fail-fast on certain non critical
sections when a resource is not available, or conversely if you are comfortable
blocking longer on a particular resource. This is not implemented in the below
`ConnectionPool::Wrapper` class.
2013-09-24 12:37:58 -04:00
2014-03-13 21:44:54 -04:00
You can use `ConnectionPool::Wrapper` to wrap a single global connection,
making it easier to port your connection code over time:
2012-03-14 12:26:39 -04:00
``` ruby
$redis = ConnectionPool::Wrapper.new(size: 5, timeout: 3) { Redis.connect }
$redis.sadd('foo', 1)
$redis.smembers('foo')
```
2012-03-14 12:26:39 -04:00
2014-03-13 21:44:54 -04:00
The wrapper uses `method_missing` to checkout a connection, run the requested
method and then immediately check the connection back into the pool. It's
**not** high-performance so you'll want to port your performance sensitive code
to use `with` as soon as possible.
2012-03-14 12:26:39 -04:00
``` ruby
$redis.with do |conn|
conn.sadd('foo', 1)
conn.smembers('foo')
end
```
2012-03-14 12:26:39 -04:00
2014-03-13 21:44:54 -04:00
Once you've ported your entire system to use `with`, you can simply remove
`Wrapper` and use the simpler and faster `ConnectionPool`.
2011-05-14 18:36:17 -04:00
2014-05-28 12:14:00 -04:00
You can shut down a ConnectionPool instance once it should no longer be used.
Further checkout attempts will immediately raise an error but existing checkouts
will work.
```ruby
cp = ConnectionPool.new { Redis.new }
cp.shutdown { |conn| conn.close }
```
Shutting down a connection pool will block until all connections are checked in and closed.
Note that shutting down is completely optional; Ruby's garbage collector will reclaim
unreferenced pools under normal circumstances.
2014-03-13 21:46:06 -04:00
Notes
-----
2014-03-13 23:31:25 -04:00
- Connections are lazily created as needed.
2014-03-13 21:46:06 -04:00
- There is no provision for repairing or checking the health of a connection;
connections should be self-repairing. This is true of the Dalli and Redis
clients.
Install
-------
```
$ gem install connection_pool
```
2011-05-14 18:36:17 -04:00
Author
2014-03-13 21:44:54 -04:00
------
2011-05-14 18:36:17 -04:00
Mike Perham, [@mperham](https://twitter.com/mperham), <http://mikeperham.com>