On Sat, Nov 26, 2011 at 2:05 PM, moses wejuli <[email protected]> wrote:
> @Les, you make a clear and concise point. thnx.
>
> In this thread, i'm really keen on exploring a theoretical possibility (that
> could become very practical for very large installations):
>
> -- at what node count (for a given pool) may/could we start to
> experience problems related to performance (server, network or even client)
> assuming a near perfect hardware/network set-up?
I think you can hit a point in number of requests in a multiget where
increasing servers doesn't help speed up that single query (because
you are limited by client cpu making the request), but having more
servers isn't actually a problem.
> -- if a memcacached client were to pool say, 2,000 or 20,000 connections
> (again, theoretical but not entirely impractical given the rate of internet
> growth), wud that not inject enough overhead -- connection or otherwise --
> on the client side to, say, warrant a direct fetch from the database?
You will likely have to worry about the persistent backend database
scaling long before that point.
--
Les Mikesell
[email protected]
