- April 22, 2007
- 9
- 0
- 60
Guys
Thanks for your assistance, but the issue I had was related to the TVServer service taking up all the available RAM and not the MSSQL database application.
During the course of a few days from a reboot this issue happened consistently regardless of OS (XP or 2K3 Server) or indeed database type (MSSQL or MySQL).
I now seem to have resolved the issue, by completing the following;
1) I changed the aerial - the signal was not ideal and did cause very occasional dropout, although this may be a red herring
2) I removed all the 'Record this program everytime on every channel' presets - this is more significant.
Previous posts have indicated the issue may be related to the EPG. The issue I noticed with my 2GHz processor was that the TVServer service accessed the SQL database every 17 seconds (peak of around 10% processor usage) when I had a number of one-off and 'Record every time on this channel' presets.
When I setup a number of 'Record everytime on every channel' presets as well the TVServer service makes a significantly higher number of table requests to the database (whichever one is used) every 17 second. The processor peaks at up to 100% and the more of this type of recording, the longer the processor stays at 100% causing even more live program and recording dropouts.
This could be either causing an issue once again with dropouts interupting the video flow, or in some way related to the EPG system and its database access. Either way the service can't release RAM and bloats.
By removing all the 'Record everytime on evey channel' presets, the processor once again dropped to 10% peaks.
3) Following another post, I found the Microsoft tool which allowed the TVServer service priority to be increased to High (NOT REALTIME) which ensures the service gets priority and according to other posts seems to make the system run more smoothly.
I think there is definately an issue (with my system) with the TVServer service accessing the database and doing a lot of record searches when 'Record Everytime on Every channel' is selected.
Whilst it is possible that my 2GHz processor is underpowered when used as a server, I think the SQL searches could be refined to spread the load and perhaps run a little less than every 17 seconds, perhaps user selectable, or hourly?
Is there anyone able to replicate this??? or better still, is anyone able to rectify the issue???
Thanks
Over a period of days my memory usage for TVService fills my available RAM (1GB) until the O/S can't run properly and eventually the machine dies.
Thanks for your assistance, but the issue I had was related to the TVServer service taking up all the available RAM and not the MSSQL database application.
During the course of a few days from a reboot this issue happened consistently regardless of OS (XP or 2K3 Server) or indeed database type (MSSQL or MySQL).
I now seem to have resolved the issue, by completing the following;
1) I changed the aerial - the signal was not ideal and did cause very occasional dropout, although this may be a red herring
2) I removed all the 'Record this program everytime on every channel' presets - this is more significant.
Previous posts have indicated the issue may be related to the EPG. The issue I noticed with my 2GHz processor was that the TVServer service accessed the SQL database every 17 seconds (peak of around 10% processor usage) when I had a number of one-off and 'Record every time on this channel' presets.
When I setup a number of 'Record everytime on every channel' presets as well the TVServer service makes a significantly higher number of table requests to the database (whichever one is used) every 17 second. The processor peaks at up to 100% and the more of this type of recording, the longer the processor stays at 100% causing even more live program and recording dropouts.
This could be either causing an issue once again with dropouts interupting the video flow, or in some way related to the EPG system and its database access. Either way the service can't release RAM and bloats.
By removing all the 'Record everytime on evey channel' presets, the processor once again dropped to 10% peaks.
3) Following another post, I found the Microsoft tool which allowed the TVServer service priority to be increased to High (NOT REALTIME) which ensures the service gets priority and according to other posts seems to make the system run more smoothly.
I think there is definately an issue (with my system) with the TVServer service accessing the database and doing a lot of record searches when 'Record Everytime on Every channel' is selected.
Whilst it is possible that my 2GHz processor is underpowered when used as a server, I think the SQL searches could be refined to spread the load and perhaps run a little less than every 17 seconds, perhaps user selectable, or hourly?
Is there anyone able to replicate this??? or better still, is anyone able to rectify the issue???
Thanks