Topic on Project:Support desk

Not exceeding the CPU quota limit

6
Summary by Stranger195

That host sucks.

Stranger195 (talkcontribs)
TheDJ (talkcontribs)

There is a $wgMemoryLimit, but no cpu limit. Also, that isn't really a common limitation to be applied by hosters for these kinds of services. Limits like these are much more common. I would ask them what this is about, since CPU limit is not something you can easily enforce yourself from PHP.

Stranger195 (talkcontribs)

This was the full reason for suspending my account:

Account themultilingualencyclopedia.16mb.com exceeded allowed 70% CPU quota limit for more than 21 times. This is considered abnormal as it causes a high server load and overall slowdown. Website must be secured and optimized or removed form the server (Account themultilingualencyclopedia.16mb.com exceeded allowed 70% CPU quota limit for more than 21 times. This is considered abnormal as it causes a high server load and overall slowdown. Website must be secured and optimized or removed form the server)
Ciencia Al Poder (talkcontribs)

Get a better hosting company, basically. That's what you get for a free/cheap hosting

Stranger195 (talkcontribs)

Good answer...

87.123.14.60 (talkcontribs)

If I was Sheldon Cooper, I would now ask "Irony?".

But no, that is no irony at all. Bad hosts offer bad services. I am not saying _your_ host is bad. All I see is that what this host offers obviously is not enough even for the standard functions of MediaWiki. Or let me put it that way: Your host wants to have more money or they will no longer allow you to use MediaWiki in that hosting account. And compared to other systems, MediaWiki is even frugal. With a reasonable host this most likely would _not_ have happened.