hi.
I have been running some tests on the performance of mod_include /
filters on
heavy traffic websites.
the test results are available at http://webpref.org/mstone/
what I did.
test situation.
1000 files of the same size, all in the same directory. (representing
our front door page news.com)
1 E4500 (8 way) box running solaris 2.6
I edited out the header and footer section of the page into virtual
include calls, and made 3 different instances
1 with no virutal includes,
1 with the header virtual included
1 with the both virtual included.
the files all pointed to the same header and footer file (which is what
it would be like in production)
raw (no filter): 341 reqs/sec load avg: max at 3.5
using Files Match to set the filter, and having the filter on the
header/footer file.
0 includes: 282 req/sec load avg: ~11
1 includes: 256 req/sec load avg: ~11.5
2 includes: 235 req/sec load avg: ~12
using Location on just the main file
2 includes: 269 req/sec load avg: ~14
using a cut down version, which has no env variables set, and only the
'include' command registered
(I commented out 2 sections of code)
2 includes: 279 req/sec load avg: ~7.1
I'm not sure if this means that ALL filters are slow, or if
it is just mod-include.
I also have some truss output for these, and I'll put them on the site
if anyone wants to see what is going on.
Cheers
Ian
