1–7

Server changes

From: Matt 9 Feb 2009 22:08
To: ALL1 of 7
35743.1
We're now on PHP FastCGI which means Apache should use less memory and hopefully shouldn't fall over as often, but I'm not guaranteeing that one.

Speed should be quite a bit better also.

That is all.
Reply
0/0
From: Matt 9 Feb 2009 22:55
To: ALL2 of 7
35743.2
Matt,

Next you switch from prefork to worker mpm on Apache make sure it is actually allowed to spawn child processes.

OK?
Reply
0/0
From: Kenny J (WINGNUTKJ) 9 Feb 2009 22:59
To: Matt 3 of 7
35743.3 In reply to 35743.2
I was gonna say - those 500 Internal Server Errors were coming up lightning fast!
Reply
0/0
From: paul 9 Feb 2009 23:13
To: Matt 4 of 7
35743.4 In reply to 35743.2
Matt,

Next you switch from prefork to worker mpm on Apache make sure it is actually allowed to spawn child processes.

OK?

Whatever that means :?

But thanks anyway Matt, your efforts, as ever, are much appreciated!

(appled)
Reply
0/0
From: Peter (BOUGHTONP)10 Feb 2009 00:39
To: Matt 5 of 7
35743.5 In reply to 35743.1
Seems to be up and down like a yo-yo. :(

Did you flick the stability switch the wrong way?
Reply
0/0
From: Matt10 Feb 2009 00:43
To: Peter (BOUGHTONP) 6 of 7
35743.6 In reply to 35743.5
I think it likes to change itself :/
Reply
0/0
From: Matt10 Feb 2009 00:48
To: ALL7 of 7
35743.7
I've put it back on prefork mpm because worker mpm seems to go nuts and I can't find a good balance of performance and resource usage.

We're still on FastCGI PHP for now, even though that doesn't appear to actually do what I thought it did, but it does save us lots of memory which is good.
Reply
0/0