I've read at length the manual about this module but in order to mantain my site alive I need to understand better what the module does concretely, so this is a list of questions and a request for a few hints.
What I'd like to know is about the concrete difference between the different throttle levels. From what I read it seems that the throttle disables the blocks and module that I checked when it reaches the maximum throttle level (5). So what's the difference between the previous levels? The module does something else to optimize the site beside disabling those modules and blocks? And it disables all the modules all at once at level 5 or there's a progession regulated in some way?
My guess is that the throttle also enables and controls the use of chached pages even in the case the site is set to not use the cache, is this true? And if I've set the site to always use the cache by default the throttle is basically useless (aside when it reaches the level 5)?
It does something else behind the scenes like slowing down the php and mySQL requests?
I ask because my hosting company disabled my account for more than a day because Drupal made the whole server crash due to an high load. I cannot understand if it was because of an unrelated problem or because my site was linked on an extremely popular board (which was), bringing an insane amount of guests all at once. So I don't know if the crash was simply due to the load, or if the load produced an overflow in the php that made a process go crazy and use up all the resources till the crash.
I've attached to the mail a report from the server that the provider sent me, I'd be glad if someone can give it a glance and tell me what could have been the problem, if it was the load, if it was a bug.
For example: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 28678 admin137 35 10 11788 11M 4532 R N 43.1 1.1 0:00 0 /usr/bin/php 28682 admin137 33 10 6812 6808 4432 R N 38.3 0.6 0:00 0 /usr/bin/php
The mySQL is not mentioned but I read that in general an high load depends on it instead that the php itself. So these php processes I've pasted here include already the CPU usage of mySQL or the problem was exclusively in the php?
Someone can help me to figure out all this? I absolutely do not have bandwidth problems, it's all about the resources usage.
-HRose / Abalieno