« Paper: Understanding and Designing New Server Architectures for Emerging Warehouse-Computing Environments | Main | 13 Screencasts on How to Scale Rails »

Sharding and Connection Pools

Hi we are looking at sharding our existing Java/Oracle based application. We are looking to make the app servers able to process requests for multiple (any?) shard. The concern that has come up is the amount of memory that would be consumed by having so many connection pools on one app server. Additionally there is concern about having so many physical connections to the database server coming from all the various app servers that may talk to that particular shard. I was wondering if anyone else has dealt with this issue and how you resolved it?


Reader Comments (1)

You could:
1. Not worry about until it becomes a real problem.
2. Profile to see if it will be problem.
3. Use non-persistent connections.
4. Buy more RAM.
5. Use an OS that effectively handles a lot of connections.
6. Add more shards to reduce the average resources per shard.

One or more of those should work.

November 29, 1990 | Unregistered CommenterTodd Hoff

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>