>> Also - hack the conf to do short runs first !
>
> Oh yeah, excellent point. That's the SPEC rc file. Look for *_TIME,
> ITERATIONS, and SIMULTANEOUS_CONNECTIONS.
My rc files usually have trial (short) values for *_TIME and a single
iteration. You can force all those in line for a compliant r
Dirk-Willem van Gulik wrote:
> SpecWeb right now follows the run book very liberally - and there are
> certainly shortcuts you could take whilst staying within the run rules. If
> you want to I can dig out a list.
It would be great if you could post such a list. Looking at SPECWeb99 dynamic
cont
> * The harder you drive the server, the more disk space you will need.
> SPECWeb99
> touches more files as you ramp up the number of concurrent connections. There
> is a formula here:
> http://www.spec.org/osg/web99/docs/users_guide.html#Pre-Inst
> Plus you need disk space for logs proportion
Ian Holsman wrote:
> i'm just about to talk to * who are going to do some static specweb
> tests with apache2
> any tips you would like to share with them ???
yeah.
* When you source the shrc file, don't expect to see any output. It just sets
some envvars.
* Look at the SPECWeb99 results
Chris Johnson wrote:
>
> Hi:
> I'm using your specweb99 modules to examine apache performance, and was
> wondering if you have newer versions handy - I noticed that the 1.3
> version did not compile on rh7.2
> (the SEMCNTR define needed to be disabled); it seemed to work
> afterwards.
Would you m
