MVP client jittery under heavy CPU utilization

[zoop]

it seems that anytime sage fires off the scheduler my server hits 99% CPU utilization for about 20-30 seconds while it figures out what it's going to do... during this time, my MVP clients get jittery, presumably due to a CPU bound portion of the server. is there any way i can help with this situation? increase the buffer for the MVP, reduce the CPU utilization during the schedule updates, etc..

thx

/jer

[_Demo_]

How much ram do you have on the server?

_Demo_

[zoop]

Originally Posted by _Demo_

How much ram do you have on the server?

_Demo_

768MB... AthlonXP2800+

[roxy99]

Your real problem is cpu utilization. Sage chokes at >90% cpu usage. You have to troubleshoot the cpu utilization. 768mb ram is tons of ram for sage.

[zoop]

Originally Posted by roxy99

Your real problem is cpu utilization. Sage chokes at >90% cpu usage. You have to troubleshoot the cpu utilization. 768mb ram is tons of ram for sage.

correct. the only process taking any CPU time _is_ sage. it seems like the scheduling/cleanup thread is hogging the CPU whenever it fires off, causing the cpu utilization to jump to 99% and stay there until it completes.

/jer

[Narflex]

Can you get logs when this happens so we can see what's actually being done in SageTV to cause that usage?

[zoop]

Originally Posted by Narflex

Can you get logs when this happens so we can see what's actually being done in SageTV to cause that usage?

attached... 21:04-7 i am seeing 99% cpu utilization by sage... there are other instances in the log as well, but all are similar...

thx jeff

/jer

[_Demo_]

Could you enable debug log by adding debug_logging=TRUE to the Sage.properties file and send the sagetv log from /opt/sagetv/server/sagetv_0.txt when the problem happens.

_Demo_

[zoop]

Originally Posted by _Demo_

Could you enable debug log by adding debug_logging=TRUE to the Sage.properties file and send the sagetv log from /opt/sagetv/server/sagetv_0.txt when the problem happens.

_Demo_

that is exactly what i posted...

debug_capture_progress=false
debug_logging=TRUE

thx

/jer

[_Demo_]

Originally Posted by zoop

that is exactly what i posted...

debug_capture_progress=false
debug_logging=TRUE

thx

/jer

Sorry about that, I had opened the wrong file. It seems your issue is cause by the hard drive running out of space so it has to delete old recordings.

_Demo_

[zoop]

Originally Posted by _Demo_

Sorry about that, I had opened the wrong file. It seems your issue is cause by the hard drive running out of space so it has to delete old recordings.

_Demo_

so... this begs the question, why is sage blocking with the CPU at 99% in order to delete files? this should be scheduled away and certainly not impact streaming, no?

thx

/jer

[zoop]

Originally Posted by zoop

so... this begs the question, why is sage blocking with the CPU at 99% in order to delete files? this should be scheduled away and certainly not impact streaming, no?

thx

/jer

interestingly, after removing my rather extensive MP3 collection from the media server these problems disappeared. seems like sage doesn't like managing 40k+ mp3 files...

just want to tip my hat at the sageTV folk, this rev is quite stable and i have even been given the nod of approval from my wife. good work folks.

thx

/jer