It's a real pain that everytime someone accesses a document
(say /usr/local/etc/httpd/docs/index.html) the server stats .htaccess
files in /usr, /usr/local, /usr/local/etc, /usr/local/etc/httpd and
/usr/local/etc/httpd/docs first.
How about the option of caching the fact that a .htaccess file does or
doesn't exist in each directory? You could nominate directories to
be cached (so ~/ directories for instance wouldn't be to allow users to
change .htaccess files immediately, others would wait until the server
was restarted).
This could be complex; but even just saying in a config file:
NoAccessFile /usr
NoAccessFile /usr/local
NoAccessFile /usr/local/etc
NoAccessFile /usr/local/etc/httpd
Would save four stats per request! Has anyone profiled Apache/Shambhala
to see how much time is wasted on these stats per request?
Mark
Mark J Cox, mark@telescope.org -- URL:http://www.telescope.org/mark.html
University of Bradford, England ---------- tel +44.1274.384070/fax 391333
(say /usr/local/etc/httpd/docs/index.html) the server stats .htaccess
files in /usr, /usr/local, /usr/local/etc, /usr/local/etc/httpd and
/usr/local/etc/httpd/docs first.
How about the option of caching the fact that a .htaccess file does or
doesn't exist in each directory? You could nominate directories to
be cached (so ~/ directories for instance wouldn't be to allow users to
change .htaccess files immediately, others would wait until the server
was restarted).
This could be complex; but even just saying in a config file:
NoAccessFile /usr
NoAccessFile /usr/local
NoAccessFile /usr/local/etc
NoAccessFile /usr/local/etc/httpd
Would save four stats per request! Has anyone profiled Apache/Shambhala
to see how much time is wasted on these stats per request?
Mark
Mark J Cox, mark@telescope.org -- URL:http://www.telescope.org/mark.html
University of Bradford, England ---------- tel +44.1274.384070/fax 391333