Juerd wrote:
Elliot F skribis 2005-05-25 10:38 (-0700):
It depends on how you're using it. If you're not using forkserver or some
persistent method, and recompiling it everytime, -w is going to add a lot
of overhead, as it checks the script when it compiles. If you're using
some sort of persistent method that avoids recompiling every time (fork
server, pperl, speedy cgi, high_perf) it shouldn't make a difference other
than when it starts up (I think).
-T adds a little bit of overhead, in that it tracks variables that came
from outside and have not been validated/cleaned. I wonder how it scales,
though, if there are thousands of connections/variables..
Both -w and -T are runtime thingies. Although -w can warn during compile
time, it can also warn during runtime. A simple example would be undef
values.
Ah, yes. I was thinking of use strict, I guess.
I use forkserver, by the way.
What was the load change? How much of a difference did it make?
