On 10 Apr 2008, at 12:44, Ruediger Pluem wrote:
Furthermore from a first glance of mod_sed I would guess that it
runs into
trouble with large static files. So could you test mod_sed with one of
the simple cases above and a 3 GB file and monitor httpd's memory
consumption
in comparison to mod_substitute?
(Hey, not everyone's filesystem can do 3GB. 3Mb should do the job!)
Easily fixed with a 5-line-or-so filter in front of it, if it's what
I think you mean.
I'd be interested in another measure: with larger number of rules
and differing matches. If noone gets there first, I might try that
myself
when I've recovered from the apachecon backlog.
As for sed-vs-simple-substitution, if the performance is no worse
than a tie,
then sed looks like a winner by virtue of power and versatility.
--
Nick Kew
