[pubcookie-dev] Load testing the threadsafe filter

[Ryan Campbell]

Executive summary:

The threadsafe filter is a tiny bit slower due to the extra setup time for
each request and it's a fair bit slower in debug mode due to the fact that
logs to the event log.  I'm actually happy with the speed, I thought the new
filter would be much slower.  As it is, I don't think it's worth spending
too much time adding speedup code.  Debug mode should only be on for
debugging; at debug=0 errors are still logged.

I'll clean up the debugging a bit more and perhaps make it less chatty at
debug=1 now that we have multiple debug levels available.

Data:

old  =  not threadsafe 3.0
new = threadsafe 3.0
none = no pubcookie filter loaded

* = some garbled debug output

Numbers are pages/second on a 900MHz stock IIS 6.0 server on a mix of asp
and static html pages.  No graphics, sounds, etc.

Clients  1        5        10       20

  no ssl, debug=0, public

none   165.32   179.52   189.73   183.31
old    148.93   145.59   145.51   145.22
new    111.39   112.29   112.01   112.23

  ssl, debug=0, public

none   47.19    50.70    55.77    50.19
old    46.84    47.83    45.74    46.98
new    44.69    44.21    44.49    44.51

  ssl, debug=0, uwetid

old    37.83    39.25    39.22    40.09
new    34.84    33.74    34.52    35.05

----------debugging on-----------------

  no ssl, debug=1, public

old    75.19    75.60*   75.90*   76.11*
new    26.97    28.96    28.77    29.16

  ssl, debug=1, public

old    35.95    34.13    36.14*   35.08*
new    19.68    19.61    19.55    19.63

  ssl, debug=1, uwnetid

old    31.21    30.89*   31.59    31.52*
new    17.24    17.21    17.20    17.28


    -Ryan