SageTVService using 880MB - is that ok?

[wayner]

I have had recent issues with slow performance in Sage. I increased my JVM size which seems to have helped somewhat. Today I was having trouble with very slow/no response from my Sage server when I noticed that the SageTVService.exe app was using 880,000 kB (accoring to Task Mgr). Should it be using that much memory or is this indicative of a problem?

My server is running Sage for WHS and has 2 GB of RAM.

[GKusnick]

Is it staying at that level or does the memory usage continue to increase without limit?

I see from your sig that you have six client UIs running on your server (not counting SageTV Client, which runs its UI locally). That can chew up a lot of memory, especially if you use a lot of graphics-heavy UI add-ons.

[wayner]

880MB is the peak (at least it is the highest that I have seen so far). I do have up to six clients but it is rare that I run more than two or three simultaneously - I normally shut off the HD-200 in the kitchen when I switch to the bedroom, etc.

[wayner]

I noticed today that it was up to 920 MB. I restarted the SageTVService and now it is at 150MB with only the UI on the server having connected so far.

By the way, the service was very slow to restart. I sometimes find that the Sage service will fail to restart and I have to reboot my server. Does anyone know why this would happen?

[JetreL]

My guess is it is trying to do a graceful shutdown and is getting caught on something that you have loaded. I would take a ten thousand foot view of what changes you have made and try to disable some of the changes to isolate what is causing the memory creep.

• Look at hardware changes
• Errors in the system logs
• Errors in Sage Logs
• Have you made any changes to any of the properties files in the past year
• Do you have SMART enabled on your HDs
• Is your server going into hibernation
• Are you running a screen saver

Those are all just shots in the dark but something is causing to use a lot of memory and the best way to isolate it is to take a large overall view of what is happening.

[vividweb]

Originally Posted by wayner

I noticed today that it was up to 920 MB. I restarted the SageTVService and now it is at 150MB with only the UI on the server having connected so far.

Mine will sit at that quite frequently. If you connect an extender and then power it off I think it keeps the extender UI in memory for a quick startup when you power that extender on again. Also make sure that your MAX Java heap is large enough because if you exceed it, you can get crashes with the sage service.