i think it's a normal problem in any tcp/ip unix/socket daemon... don't
have ram? add swap... it's a hardware limit not a software limit...
maybe instead of 'use swap' we could add a 'more than xMB use disk instead
of ram', but you will get into a problem of disk latency, etc... it's like
any database writing temporary query results in memory and after a limit
put the result in disk instead of a memory result

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to