Marc Schmidt wrote: > > hi all, > > after writing and starting a little performance test client and running > it against squid, > the poor little fish stops doing what he is supposed to do: serving the > requests. > > the setting is something like this: > the test client is written in java (using jdk1.4.0) > there are 20 threads (each simulating a web client) > each thread requests 50 times the same url > the os is linux suse 7.3 > the squid configuration is the one that gets shipped (standard squid.conf) > > when using 20 threads with 10 iterations per thread everything is fine. > > so, for my five pens this is more or less a configuration issue. isn't it? > > anybody out there with a proper squid.conf file that is prepared to > startup squid in > a high performance mode? or does anybody know what conf parameters to screw? > > help's appreciated > > cheers marc
Which version of squid are you testing ? What's in access.log during the problem test window ? More important : anything in cache.log ,during the problem phase ? There is no high performance mode squid.conf so to speak, because squid is always high performant... A standard squid.conf as shipped can not work I think, at least a listening port for requests must be specified. What about cache sizes used etc ? M. -- 'Time is a consequence of Matter thus General Relativity is a direct consequence of QM (M.E. Mar 2002)
