For me, "1200 sec / day of processor time" and "180 sec / day of sql-query time" unfortunately does not say anything, and this is one of the characteristics of the hosting tariff. I would like to know, at least approximately, how many of the above resources are consumed by the average websites or to get some information on the induced characteristics.
Well, the average "price" of the sql request (of course, depends strongly on the quality of the request) - maybe 0.007 seconds, or maybe 0.3 seconds (requests are taken from the samopisny php site, unfortunately the popular cms will not be given). If in the second case, taking into account 180 seconds, then this is clearly not much.
Most likely this is the average figure taken from hosting statistics. Useful information can not be called. I think you should ask this question to comrades from ho.ua
Please note one nuance: the source software (MySQL, apache) does not include the calculation of processor time, you can only configure the timeout, but I think it has nothing to do with this issue. It turns out that these conditions are trying to somehow "frighten" the client so that he does not squander the processor time. Take, for example, the ISPmanager control panel. There is a processor time limit function that creates a user-specific configuration file (PHP) php.ini and in the variable max_execution_time sets this restrictive value. But sometimes this restriction can be bypassed by calling set_time_limit (NULL). And in my opinion it’s difficult to calculate the total CPU time spent in my opinion, which is difficult and resource-intensive, since each request has to be intercepted. In short, to put it clearly, all this is nonsense, twist as you wish. )))
Source: https://ru.stackoverflow.com/questions/13642/
All Articles