Re: svn commit: r468373 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_cache.c modules/cache/mod_cache.h modules/cache/mod_disk_cache.c modules/cache/mod_disk_cache.h modules/cache/mo

2006-10-27 Thread Greg Marr
At 01:41 PM 10/27/2006, Davi Arnaut wrote: Niklas Edmundsson wrote: And when you have a file backend, you want to hit your disk cache and not the backend when delivering data to a client. People might think that this doesn't matter, but for large files, especially larger than RAM in your

Re: svn commit: r468373 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_cache.c modules/cache/mod_cache.h modules/cache/mod_disk_cache.c modules/cache/mod_disk_cache.h modules/cache/mo

2006-10-27 Thread Davi Arnaut
Greg Marr wrote: At 01:41 PM 10/27/2006, Davi Arnaut wrote: Niklas Edmundsson wrote: And when you have a file backend, you want to hit your disk cache and not the backend when delivering data to a client. People might think that this doesn't matter, but for large files, especially larger

Re: svn commit: r468373 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_cache.c modules/cache/mod_cache.h modules/cache/mod_disk_cache.c modules/cache/mod_disk_cache.h modules/cache/mo

2006-10-27 Thread Davi Arnaut
Davi Arnaut wrote: Greg Marr wrote: At 01:41 PM 10/27/2006, Davi Arnaut wrote: Niklas Edmundsson wrote: And when you have a file backend, you want to hit your disk cache and not the backend when delivering data to a client. People might think that this doesn't matter, but for large

Re: svn commit: r468373 - in /httpd/httpd/trunk: CHANGES modules/cache/mod_cache.c modules/cache/mod_cache.h modules/cache/mod_disk_cache.c modules/cache/mod_disk_cache.h modules/cache/mo

2006-10-27 Thread Graham Leggett
Davi Arnaut wrote: Because the data is already in memory. Why should I write something to disk, erase it from memory, and read it again shortly ? Why should I take care of something that is the job of the OS ? Why should I trash the VM constantly ? Because reading slowly from a cache disk is