Large caches ...
brad at danga.com
Sat Jul 2 00:30:39 PDT 2005
You know that memcached isn't a database, right? It's a CACHE. If a
machine dies, you get some cache misses, which you then have to repopulate
from your REAL DATABASE.
On Sat, 2 Jul 2005, Hans-Juergen Schoenig wrote:
> We are planning to develop an application on top of a very large in
> memory database. Basically the size of the application will be around
> 100 - 400 gb (in memory). We will need a quite large server farm to
> achieve that. The problem now is: What happens if a server fucks up?
> What can we do to make this work 24x7? Rebuilding the cache from scratch
> is not an option as it is too large :(.
> How did other folks solve that?
> Best regards,
More information about the memcached