On Tue, 2005-03-15 at 17:47 +0000, Martin Moss wrote: > I haven't used Memchache yet, but it has nothing to do > with databases.... > It CAN be used to prevent database load, OR it could > be used to prevent too much access to flocking > files...
This is true, but it sounds like Andre wants to replace a bespoke database structure with something else, and Memcached should not be considered for that. It has no permanent storage, no failover, and will silently drop data if it runs out of space. Good for caching, lousy for database storage. I agree that a low-impact RDBMS like MySQL is an obvious choice here, but the fastest choice if it only needs to run on one machine would be BerkeleyDB. In my benchmarks, it is one of the fastest methods of shared storage available from Perl. IPC::MM is fast, but not really maintained anymore. Cache::FastMmap is fast, but will drop things over the allocated cache size limit, just like Memcached will. So, I recommend BerkeleyDB or MySQL. - Perrin
