Yecheondigital | 9 Aug 2012 08:21
Picon
Favicon

Slow and unusable Wiki after upgrading to 1.19

Recently I tried upgrading to mediawiki 1.19 on a shared server (hosted by Dreamhost). After upgrading to
1.19, my site was sooooooooo slow that it was barely operable. Pages would rarely successfully load and
most would eventually turn into a "not found", 500 error.

Here is an excerpt from the log kept by our Process Watcher, the daemon that is
killing your troublesome php5.cgi processes:

Tue Aug 7 11:15:29 2012 procwatch3 INFO: PID 27983 (php5.cgi)
kingkwon:pg505086 - 36.4MB ram, 2.73 sec cpu [idle php]: killed for uid
ram

Tue Aug 7 11:15:49 2012 procwatch3 INFO: PID 29184 (php5.cgi)
kingkwon:pg505086 - 36.7MB ram, 1.12 sec cpu: killed for uid ram

Tue Aug 7 11:15:49 2012 procwatch3 INFO: PID 29073 (php5.cgi)
kingkwon:pg505086 - 36.6MB ram, 0.89 sec cpu: killed for uid ram

Tue Aug 7 11:15:59 2012 procwatch3 INFO: PID 28477 (php5.cgi)
kingkwon:pg505086 - 35.4MB ram, 2.48 sec cpu [idle php]: killed for uid
ram 

Tue Aug 7 11:15:59 2012 procwatch3 INFO: PID 29079 (php5.cgi)
kingkwon:pg505086 - 33.5MB ram, 1.40 sec cpu [idle php]: killed for uid
ram 
Kills prior days:

/var/log/procwatch.log.1.gz:7102

/var/log/procwatch.log.2.gz:4569

(Continue reading)

Marcin Cieslak | 11 Aug 2012 10:12
Gravatar

Re: Slow and unusable Wiki after upgrading to 1.19

>> Yecheondigital <yecheondigital <at> yahoo.com> wrote:
> Recently I tried upgrading to mediawiki 1.19 on a shared server (hosted by Dreamhost). After upgrading to
1.19, my site was sooooooooo slow that it was barely operable. Pages would rarely successfully load and
most would eventually turn into a "not found", 500 error.
>
> Here is an excerpt from the log kept by our Process Watcher, the daemon that is
> killing your troublesome php5.cgi processes:

Are you running PHP as CGI? Do you have possibility to use something else? (although with your traffic I
don't think it's a problem...)

> -My site: Koreanwikiproject.com
> -We get around 1,400 hits a day.
> -I would occasionally have problems with slow loading and processes
> getting killed. I originally thought this was due to people possibly
> using the pdf converter plugin. However when I had 1.19 installed, I
> hardly had any plugins installed as I was doing a fresh install then
> copying my image files over.
> -No caching has been enabled.

I can see right know you are running 1.17alpha and it was pretty slow
to me as well.

Can you post your LocalSettings.php (without passwords etc.)?

Can you tell us something about how your database is behaving?

Did you try to disable all extensions and check if it's faster
and then enable them one-by-one to see if something's there is causing
a problem?
(Continue reading)

Yecheondigital | 13 Aug 2012 14:07
Picon
Favicon

Re: Slow and unusable Wiki after upgrading to 1.19

Marcin,

Thank you for your response. Yes I downgraded back to 1.17 alpha after originally upgrading to 1.19.

After upgrading to 1.19, I didn't reinstall many of the extensions. I only uploaded a handful. I also let it
generate a new localsettings file and I added the small amount of extensions I was using back into the file.
However because it was so slow, I had no choice but to downgrade again. So I don't think it's an extension
problem, though I could be wrong.

And yes PHP is ran as cgi. Another person on here did send me a link to: http://blog.dreamhosters.com/kbase/index.cgi?area=2933

But that says running it as apche has security problems and "It's just as fast as running PHP as an Apache
module, and we include more default libraries."

Thanks,

Chris

________________________________
 From: Marcin Cieslak <saper <at> saper.info>
To: mediawiki-l <at> lists.wikimedia.org 
Sent: Saturday, August 11, 2012 5:12 PM
Subject: Re: [MediaWiki-l] Slow and unusable Wiki after upgrading to 1.19

>> Yecheondigital <yecheondigital <at> yahoo.com> wrote:
> Recently I tried upgrading to mediawiki 1.19 on a shared server (hosted by Dreamhost). After upgrading to
1.19, my site was sooooooooo slow that it was barely operable. Pages would rarely successfully load and
most would eventually turn into a "not found", 500 error.
>
> Here is an excerpt from the log kept by our Process Watcher, the daemon that is
(Continue reading)

Benjamin Lees | 11 Aug 2012 23:28
Picon

Re: Slow and unusable Wiki after upgrading to 1.19

Your CGI processes were being killed because your user was using too much
memory. (When a CGI process is killed, the Apache connections will time out
and give a 500 error.)  Adjust the number of processes that are spawned
(which you might or might not be able to do, depending on how much fiddling
DreamHost lets you do), split your sites between more users, or contact
DreamHost support.

On Thu, Aug 9, 2012 at 2:21 AM, Yecheondigital <yecheondigital <at> yahoo.com>wrote:

> -No caching has been enabled.
>
That's probably not good!

I will eventually be moving to VPS but I'd like to make sure this same
> problem doesn't carry over to the VPS.
>
It won't.

Gmane