[Date Prev][Date Next][Thread Prev][Thread Next][Interchange by date
][Interchange by thread
]
[ic] Should I buy another CPU?
<SNIP>
> > <music@labyrinth.net.au> writes:
> >
> > > I would really like to try the (RPC mode, MaxServers 0) solution and
> > > see how it goes before investing in more hardware, particularly as
> > > it is suggested that it may not be a hardware problem.
> >
> > ,----[ interchange.cfg ]
> > | # Set to "low", "high", or "rpc" to get different server parameters.
> > | Variable TRAFFIC rpc
> > |
> > | ifdef TRAFFIC =~ /rpc/i
> > | Message RPC traffic settings.
> > | PreFork Yes
> > | StartServers 5
> > | MaxServers 0
> > | MaxRequestsPerChild 100
> > | HouseKeeping 2
> > | PIDcheck 120
> > | endif
> > `----
> >
> > I'm not sure if the StartServers config of 5 will conflict with the
> > MaxServers of 0.
>
> I don't *think* that it will conflict. MaxServers 0 isn't actually
> setting the MaxServers to 0, it's setting it to unlimited. As Mike
> explained it means that Interchange will not use two of the Perl signals
> to determine the number of running servers, it will spawn as many as it
> needs.
</SNIP>
I've been running with that exact configuration (StartServers 5) and the
MaxServers 0 setting since the patch was found. No problems to report.
...and conversions have improved by 5% with no additional changes
through Verisign! THANK YOU MIKE AND RON!
Whether new hardware would have aleviated the symptoms or not I would
rather have this patch in and not have to worry about sometime in the
future when the server is loaded more. I'm running a PIII 800, 1G RAM
and SCSI RAID - sure, I could throw some more RAM at it or upgrade the
processor, but then I would feel like a M$ user... ;-)