Post by Lanthar D'Alton on Oct 10, 2004 14:12:58 GMT -5
Accidentally deleted Chass' post... which said:
****************************************************************************************
CPU Eating Resources
« Thread started on: Oct 9th, 2004, 04:50am »
--------------------------------------------------------------------------------
I was looking through my old logs and noticed that:
| >lds_spch_runonc 305935 msec 45315 calls |
This gets called a lot . ( which I know of but..)
The Msecs it takes is well.. crazy.. and can eat CPU usage like crazy.. any way of reducing this?
****************************************************************************************
that script is called once per second
and that means your server was up and running for about 45000 seconds
and that means that it used 300000 milliseconds
which means...
it used 6 milliseconds per call
so, yes it appears to use a lot of time, but it is VERY VERY VERY VERY efficient and it calls itself once per second so it is running for .0006 seconds once a second.
cpu usage is so minimal as to be ignored.
Put another way, the script used 300 seconds of 45000 to parse everything that was said the entire time the server was up, which is 6/1000 of the total cpu used by the server.
Anyway, that's less than 1% of the cpu.
In terms of lag, the average time used by it is that same 6/1000 of a second once a second, which probably won't even show up in windows task manager's cpu chart.
-Lanthar
****************************************************************************************
CPU Eating Resources
« Thread started on: Oct 9th, 2004, 04:50am »
--------------------------------------------------------------------------------
I was looking through my old logs and noticed that:
| >lds_spch_runonc 305935 msec 45315 calls |
This gets called a lot . ( which I know of but..)
The Msecs it takes is well.. crazy.. and can eat CPU usage like crazy.. any way of reducing this?
****************************************************************************************
that script is called once per second
and that means your server was up and running for about 45000 seconds
and that means that it used 300000 milliseconds
which means...
it used 6 milliseconds per call
so, yes it appears to use a lot of time, but it is VERY VERY VERY VERY efficient and it calls itself once per second so it is running for .0006 seconds once a second.
cpu usage is so minimal as to be ignored.
Put another way, the script used 300 seconds of 45000 to parse everything that was said the entire time the server was up, which is 6/1000 of the total cpu used by the server.
Anyway, that's less than 1% of the cpu.
In terms of lag, the average time used by it is that same 6/1000 of a second once a second, which probably won't even show up in windows task manager's cpu chart.
-Lanthar
