Sage getting slow

[Poseidon88]

Over the last few months, I've noticed that sage is running a lot slower on my HTPC. I frequently get the spinning Sage icon when doing things like skipping forward or back, stopping playback, opening the program guide, etc. Frequently, the pause lasts several seconds. A few times it has paused for over a minute.

Is it possible that the database has grown to an unwieldy size? I checked, and the wiz.bin file doesn't seem all that big (about 9 MB), but I've been running Sage pretty much continuously for almost 3 years. I have no idea what is a reasonable size.

Any other suggestions? Known ways to improve performance?

[BobPhoenix]

The biggest performance boost for me was upgrading Java 1.4.2 to 1.6.0! Night and Day speed increase!

[sakker]

This is probably a big unanswered question with many and no solutions.

I had a rock solid fast performer for a long time, then all of a sudden I was having the spinning icon when stopping a movie, moving back a menu, all kinds of things. I couldn't fix it so I just learned to deal with it. All of a sudden out of the blue 3 weeks or so ago it went back to being super quick, no spinning circles again. No updates, nothing new... go figure.

[Ryokurin]

Do you use sleep? It typically happens to me after a week or so of doing that. Typically its because the swapfile just keeps on growing. If you have it set to a fixed size windows will eventually popup an error saying you need to increase it. Typically a reboot fixes it. I just in the habit of doing it when I notice it slow, or just not using sleep.

[MrD]

Originally Posted by Poseidon88

Over the last few months, I've noticed that sage is running a lot slower on my HTPC. I frequently get the spinning Sage icon when doing things like skipping forward or back, stopping playback, opening the program guide, etc. Frequently, the pause lasts several seconds. A few times it has paused for over a minute.

Is it possible that the database has grown to an unwieldy size? I checked, and the wiz.bin file doesn't seem all that big (about 9 MB), but I've been running Sage pretty much continuously for almost 3 years. I have no idea what is a reasonable size.

Any other suggestions? Known ways to improve performance?

I feel your pain brother! I asked a similar question earlier in the month. I have the same exact issue.

I am using JRE 1.5 and I have 2Gigs and Core Duo 2. My media extender and PC clients slooooooooow done browsing the menus constantly. It is the rule not the exception now.

I have no idea what the issue is, but I can speculate it may have something to do with a database (i.e. wiz.bin) that needs to be re-indexes and compressed (i.e. remove the deleted rows).

I'd love to have a solution to this problem. Starting over with a fresh install is not an answer, especially since we do not have a root cause.

[toricred]

You should upgrade to JRE 1.6 Update 3. I found major speed improvements when I did that.

[MrD]

Originally Posted by toricred

You should upgrade to JRE 1.6 Update 3. I found major speed improvements when I did that.

Just upgraded client and server machines... Spinny is still there

[BobPhoenix]

Originally Posted by MrD

Just upgraded client and server machines... Spinny is still there

Did you uninstall old version of Java? They are not removed when a new version is installed.

[MrD]

I turn it "off" by renaming the folder "jre1.5.0_06.stop", besides the registry points the JRE loader to the current JRE. I use this trick at work all the time, because I have to support software written on multiple Java platforms.

You can also "test" the active JRE by trying to rename the folder while Sage is running. You will get an access denied error message for the active JRE.

The bottom line is jre1.6.0_03 is being used

[BobPhoenix]

Originally Posted by MrD

I turn it "off" by renaming the folder "jre1.5.0_06.stop", besides the registry points the JRE loader to the current JRE. I use this trick at work all the time, because I have to support software written on multiple Java platforms.

You can also "test" the active JRE by trying to rename the folder while Sage is running. You will get an access denied error message for the active JRE.

The bottom line is jre1.6.0_03 is being used

That's fine! Some people don't know how to select a specific JRE like this - I was just checking.

[MrD]

I am beginning to wonder if this is actually a threading problem.