Question

I’m creating a web application running on a Linux server. The application is constantly accessing a 250K file – it loads it in memory, reads it and sends back some info to the user. Since this file is read all the time, my client is suggesting to use something like memcache to cache it to memory, presumably because it will make read operations faster.

However, I’m thinking that the Linux filesystem is probably already caching the file in memory since it’s accessed frequently. Is that right? In your opinion, would memcache provide a real improvement? Or is it going to do the same thing that Linux is already doing?

I’m not really familiar with neither Linux nor memcache, so I would really appreciate if someone could clarify this.

Answer 1

Yes, if you do not modify the file each time you open it.

Linux will hold the file’s information in copy-on-write pages in memory, and “loading” the file into memory should be very fast (page table swap at worst).

Edit: Though, as cdhowie points out, there is no ‘linux filesystem’. However, I believe the relevant code is in linux’s memory management, and is therefore independent of the filesystem in question. If you’re curious, you can read in the linux source about handling vm_area_struct objects in linux/mm/mmap.c, mainly.