Ved wrote:
Thanks David for your reply but what I mentioned are not my
assumptions
1. memcached is installed on the machine where my file is so that
takes care of your concern ( memory on a different machine ).
That doesn't matter - you still go through the same client/server
motions to access it through a socket as if you have distributed storage.
2. I am not just reading a single file everytime. I have 3 data files
that I access in the script (system may be caching files in memory)
3. Even if the files are not changing does it mean that disk cache is
faster than memcached? that too an extent of disk cache being almost
50% faster than memcached.
Yes, if you have sufficient RAM, all recently accessed file data will be
cached at the OS level for fast repeated access.
I am sorry, but I don't think your explanation addresses my concerns.
The part that didn't make sense was that you mentioned memcache having
many failures. Unless you have not provided sufficient RAM, you should
only fail on the first access to new or expired data. Perhaps with
memcached running you don't have enough memory to hold your active data
set in either the memcache cache or the now reduced filesystem buffers
and end up making them both thresh.
--
Les Mikesell
lesmikes...@gmail.com
