strace of SPECWeb99 static workload

2002-10-30 Thread gregames
Here is an strace of the static portion of the SPECWeb99 benchmark. http://www.apache.org/~gregames/strace.spec_static This includes two keepalive connections with multiple requests on each connection, with Apache 2.0.43 running on a Red Hat 7.2 box. The number preceding the syscall is the

RE: strace of SPECWeb99 static workload

2002-10-30 Thread Bill Stoddard
Here is an strace of the static portion of the SPECWeb99 benchmark. http://www.apache.org/~gregames/strace.spec_static This includes two keepalive connections with multiple requests on each connection, with Apache 2.0.43 running on a Red Hat 7.2 box. The number preceding the syscall is the

Re: strace of SPECWeb99 static workload

2002-10-30 Thread Roy T. Fielding
One of them is probably here (in function ap_meets_conditions). Is there any reason we cannot use r-request_time here? I can't tell for sure right now, but the original concern was that dynamically generated pages that are forked into a cache (something done by RobH for IMDB) would have a

RE: strace of SPECWeb99 static workload

2002-10-30 Thread Bill Stoddard
On 30/10/02 22:06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: The disk files aren't closed until the connection terminates. I assume we're using the connection pool for some file structure. It's probably not a big deal for prefork, but for a threaded MPM it could result in a lot of open