On Wed, 21 Apr 1999, Gavin M. Roy wrote:
> Am running a Dual PII-300MHz 256mem Webserver in production. This box gets
> over 2M hits a day. Base installation was Slackware (3.5 I presume). Runs
> great on 2.0.35, except it locks when the kernel is compiled with SMP
> enabled. I can compile 2.0.36, it error's out in main.c. I can compile any
> 2.2.x kernel, and was running 2.2.6 since Sunday. But like the 2.2.x
> kernels before it, Apache starts acting really funky. The number of
> processes increase, and it stops accepting connections. Not too good for a
> webserver that does 550K to 600K uniques a day. :( Any suggestions or
> information I could provide for better resolution that running 2.0.35 on one
> cpu?
>
> Thanks
>
> Gavin
>
Try Slackware 3.6
I tried the 2.1.x kernels with slack 3.5 and dident have much luck (SMP
kernels). Slack 3.6 is 2.2.x ready with the exception of its pppd (which
I dont think that you need anyway). I guess you could go ahead and update
slack 3.5 to be 2.2.x ready, but for me it was easier to just re-install
then re-compile everything. I am currently running Slackware 3.6 with
kernel 2.2.5 SMP. also I did run the 2.0.36 kernels on slack 3.5 without
problems.
as far as Apache goes, with such a heavy workload, you probably need to
tune the config files quite a bit. sorry but I dont have any expearance
with tuning Apache for heavy workloads.
Jon C Wade.
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
