You can use the -I option to increase the max object size (it defaults to
1mb), but that will reduce the overall memory efficiency. So you still
shouldn't set it too high.
If your server has 96G of ram, you still need to leave some left over for
the OS, memcached's hash table, connection management, buffers, and TCP
sockets. So I'd put that closer to 92G or 90G for memcached.
It shouldn't be hard to prototype and see if it'd help? It's not clear if
you have multiple servers accessed this shared data, or if it's just one
process accessing the same information multiple times, etc.
-Dormando
memcached can handle that no problem- there are much larger and busier instances in production out there.
my one question, though, would be why are you caching the xml instead of parsing it and caching the resulting data? it seems silly to parse the same thing multiple times.
awl