Slow MVP

[dadams]

Since version 6.1 my MVP's are very slow and non-responsive. They flow through the main menu okay. If I select a recording to play, it takes approximately 15-20 seconds to register the 'browse files' command, then another 15-20 seconds to select 'watch now'. This is extremely frustrating. Any ideas?

[MeInMaui]

If you haven't already, try upgrading your java version to 1.6 on your server. The MVP is significantly faster using this version.

Aloha,
Mike

[dadams]

Thanks, Mike. That seemed to work. It was hard for me to explain to my 6 year old why she had to wait for each click when she wanted to watch "Max and Ruby"

[TBoneJones]

I've been noticing slowness after installing 6.2.10. Specifically I have issues when the it has been idle for a bit and the picture view screen saver kicks in (cycles thru "my pictures"). I get a black screen instead of the pictures. From the main menu I can browse to "my pictures" and view them without a problem, but the auto screen saver doesn't seem to work. I'm going to get the server running in debug mode shortly, but just figured I would send this out in case anyone else has seen this.

My setup -
SageTV running in service mode on server in basement
My Picutres/My Videos pointing to a share on a WindowsHomeServer box
2 MediaMVP and 1 placeshifter client around house (all three have issue)
6.2.10 with 6.3.3c MCE 16x9

[gplasky]

Just like the post above, make sure you're running java 1.6. Sage comes with an older version. If you just used that, upgrade.

Gerry

[Taddeusz]

One thing you can do is check to see how large your JVM Heap Size is getting. 200MB is the default size. But if it starts bumping into that it will slow things down. Particularly on the MVP. If you go to Settings -> Help -> System Information. Then scroll down a bit. You'll see a number like 100MB/150MB/200MB. For example I had to up mine so right now it reads 219MB/257MB/533MB. You'll want to pay attention to the middle number. If that number reads the same as the last number (max heap size) you'll definitely want to up it. My MVP and Placeshifter got quite a bit more responsive after I upped it on my server.

[BFisher]

Hey Taddeusz - very interesting! I have 5 MVPs... and while they aren't fast, they aren't too bad (could be more responsive). I checked my numbers... 53/82.

How do I bump this number up? Is there a way to tell how high should I go?

Thanks!

[Taddeusz]

What I would do is start up all 5 MVP's if you can. Or however many MVP licenses you have. Then check and see how large the second number is compared to the max. If it's not going over 200MB I wouldn't necessarily worry about it. If the second number is exactly 200MB, in othe words the same as the max, then the maximum heap size needs to be made larger.

Large music libraries cause the heap size to be large.

[Taddeusz]

Sorry, to change the maximum heap size run regedit and go to:

HKLM\software\Frey Technologies\SageTV

Change the value in JVMMaxHeapSizeMB to 0x200 (decimal 512). The value that shows up in SageTV for some reason will now be 533MB.

[MeInMaui]

Originally Posted by Taddeusz

Sorry, to change the maximum heap size run regedit and go to:

HKLM\software\Frey Technologies\SageTV

Change the value in JVMMaxHeapSizeMB to 0x200 (decimal 512). The value that shows up in SageTV for some reason will now be 533MB.

Just make sure you have enough RAM to go with that.

[BFisher]

I have 2 GB of RAM, I assume that's enough. Sorry, I'm not experience with Java - is there any negative to doing this? Like I said, my MVPs are slow, but acceptable... my wife will kill me if I mess something up on "her" Sage system But if I could make them faster - that'd make me happier! 53/82 seems really low based on the numbers you shared.
Thanks!

[Taddeusz]

Originally Posted by BFisher

I have 2 GB of RAM, I assume that's enough. Sorry, I'm not experience with Java - is there any negative to doing this? Like I said, my MVPs are slow, but acceptable... my wife will kill me if I mess something up on "her" Sage system But if I could make them faster - that'd make me happier! 53/82 seems really low based on the numbers you shared.
Thanks!

It's probably mostly because of the almost 8000 songs in my music library.

[biren]

I have the same problem since I updated to 6.2.10.
I have Java 1.6.03 installed, and I have all the previous versions disabled (Using the JVM control panel). I have rebooted the SageTV server and the MVP a few times but it doesn't make a difference.

I have a Core Duo 2.4GHz, and 3GB of memory, so I don't think that's the problem, my JVM also uses about 64MB out of the 200MB allowed, and in the as a whole (SageTV Service) takes 135MB (From Windows Task Manager).

Any help will be very useful.

[phornung]

This happens to me as well, but my lone MVP seems to become more responsive if I turn off the caption playback and comskip playback. With the two enabled, watching any show >2 hours is agonizing!

I hope my symptom is similar to yours, and this helps. If it isn't, then consider that my problem is probably different.

EDIT: I noticed that I was running the old java version and using the default heap size (registry=0, max is really 200mb). I'll report back how things go now that my settings are right.

[GbrNole]

sage 6.2 and 6.3 definitely seem to be slower in MVP responsiveness than sage 6.1 versions (using java 1.6). i almost feel like i'm using an old directv 32-bit receiver when i scroll the guide now!

[phornung]

Things were noticeably faster, but still not smoothly fast. I have quite a delay bringing up the menu to disable captions in order to make the video play without skips.

The only noticeable bottleneck is my processor on my server, where Sagetv.exe was pegged, but I wasn't recording or watching locally. The only thing running was the remote MVP. Also, I notice the menus seem to fade in, but I wouldn't think that's where the CPU is being taxed heavily from.

I never remember it being this way with v.5.

EDIT: It would help to mention that my server's processor is a Sempron 2500+. I'd expect that would be enough to stream video to a media extender, since I've worked with much less in the past.