partitioned db pool

[fwbrasil]

The single threaded approach became a bottleneck for me.

fixes #58

[mauricio]

@fwbrasil could you get some docs on how it works and why someone should pick this one?

[fwbrasil]

@mauricio I was thinking about this. Maybe we should not allow or discourage the usage of the SingleThreaded pool. The partitioned pool overhead is low and if necessary, it is possible to use it with partitions = 1. Wdyt?

[mauricio]

That makes sense. I'm going to do the other async stuff this week and we
can deprecate this.

Em segunda-feira, 12 de maio de 2014, Flavio W. Brasil <
notifications@github.com> escreveu:

@mauricio https://github.com/mauricio I was thinking about this. Maybe
we should not allow or discourage the usage of the SingleThreaded pool. The
partitioned pool overhead is low and if necessary, it is possible to use it
with partitions = 1. Wdyt?

Reply to this email directly or view it on GitHubhttps://github.com//pull/88#issuecomment-42809175
.

Maurício Linhares
http://mauricio.github.io/ - http://twitter.com/#!/mauriciojr

[fwbrasil]

@mauricio can we merge this pr?

[mauricio]

@fwbrasil can you include scaladoc for the class itself explaining it's usage?

[fwbrasil]

@mauricio Sorry, I forgot about the scaladoc, will provide it.