Client GUI Slow

[Skirge01]

I recently virtualized all my computers under vSphere 5. Since doing so, Sage hangs with the spinning circle pretty regularly on the client. All the reports on the server seem to indicate there's no bottleneck there (memory, network, disk, or cpu). I did not reinstall Sage on the client PC, so the first thing I'm going to try is uninstalling all plugins on the client and reinstalling them one at a time.

However, I changed all my UNC paths and I'm wondering if there could be remnants of obsolete paths lying around someplace, bogging down the system. For example, I did find that the fanart folder's new UNC path was correct in the BMT web UI, but the client plugin had it as the old path. Is there a way to check for other instances like this? Are paths stored in the wiz.bin file on the client or anywhere else?

[Fuzzy]

Originally Posted by Skirge01

I recently virtualized all my computers under vSphere 5. Since doing so, Sage hangs with the spinning circle pretty regularly on the client. All the reports on the server seem to indicate there's no bottleneck there (memory, network, disk, or cpu). I did not reinstall Sage on the client PC, so the first thing I'm going to try is uninstalling all plugins on the client and reinstalling them one at a time.

However, I changed all my UNC paths and I'm wondering if there could be remnants of obsolete paths lying around someplace, bogging down the system. For example, I did find that the fanart folder's new UNC path was correct in the BMT web UI, but the client plugin had it as the old path. Is there a way to check for other instances like this? Are paths stored in the wiz.bin file on the client or anywhere else?

On the client, all paths are basically stored in the sageclient.properties file stored on the client itself. It only really depends on the server for the actual media information.

[Skirge01]

Good to know. I did a quick search and only one thing showed up, which I fixed. However, even after uninstalling all client plugins, the hang is still happening. I'm including a copy of my client's log file, in case someone can identify the cause of the UI hangs shown or at least where I should start looking.

[Fuzzy]

You sure you uninstalled all plugins? There looks to be a LOT of plugins loading in that log file.

[Skirge01]

Originally Posted by Fuzzy

You sure you uninstalled all plugins? There looks to be a LOT of plugins loading in that log file.

Hehe... that was after I reinstalled them. I'll post one without any plugins when I get home.

[Skirge01]

I was going to post the log file when I decided to try using the SageTV UI on the server and see how responsive it was. I found it's also slow there, even with all the animations turned off. So, even though vSphere's graphs don't seem to be showing a bottleneck, there may be one on a graph I simply haven't looked at. Because I'm rebuilding the server anyhow, I'm not going to waste too much time on tracking this down. If the new server exhibits the same issues, I'll post again in this thread.

Thanks for taking a look though, Fuzzy!

[Skirge01]

I just got a notice from WHS 2011 that my SageTV VM had only 10% disk space left on the C: drive. Hmmm... could this be why the system has been so slow? It sure could be! That'd be pretty cool, even if it is one of those ::facepalm:: moments.

I logged in remotely and I'm currently running a disk cleanup just to quickly get things tidier (Wow, there was a LOT to clean up). When I get home, I'll expand the C: drive of that VM and see how responsive Sage becomes.

[Fuzzy]

It is bad to let the C drive get too full, and even worse if it gets completely full. What can happen if the drive is full, Sage may not be able to write out it's update of the sageclient.properties files, and they will revert back to defaults. I've had this happen before back when I was running a sage client off a CF card, and then a few other times after moving some files around and then updating a bunch of fanart cache's.

[Skirge01]

Yep. But, it turns out that wasn't the issue. I tripled the space on the drive and it's just as slow. It turned out to be a great test, though, as I decided to back up my existing VM via WHS 2011 and restore it to a new VM. It took about 2 hours with all the "nuances" I ran into and needed to account for. I think the next one will take about 30 mins, if I don't need to do a backup first.

At this point, I'm holding off on troubleshooting until the new server is in place. I did take note that the hang occurs primarily and the worst when stopping playback of a completed recording.