JVM Heap Size - Different on PC Server vs HD300 Extender

[hackzaw]

I was getting an error saying "Out of Memory" back on 05/13. I'm running the latest versions with Diamond. Also, my server is Windows 7 64 bit if it matters with 8 Gig ram

So I saw a thread detailing how to increase Java Heap Size (including the 64 bit version), and changed it on the PC. Went to the Wow6432node in regedit, and changed the value of JVMMaxHeapSizeMB to 300.

On the HD300 extender if I go into Info at the home screen, I would see the 700 (oddly, I just went to check it, and it's now showing 292MB/400MB/400MB for Used/Total/Max - I swear it said 700 as max early).

And what I thought was odd, was on the desktop, it was always showing 400 as the max, when it should have showed 700 like the extender did. After changing it in regedit, I rebooted everything (PC, HD300)

Checking the value now in regedit it showed 300 as the current setting, but only 400MB as the max (now in both the PC and the extender).

Thoughts?

[jorton]

I may be missing something in your post but if you are getting out of memory errors (I assume these were in Sagetv not just general windows errors) that you should be setting the java heap to "1024" not "300", I thought that the default Sagetv heap size was 392(???) or something, so trying to set to "300" would not allocate more memory to Sagetv, it would be trying (if even possible) to set the java heap to less than default. We recommend setting the java heap to "1024" on the server and clients with Diamond. You have 8GB ram, you should have no problem with 1024 as the heap size.

Good luck,

J

[hackzaw]

Thanks for the response. When I reference the "300", I was indicating that was the setting I entered was "300" hex which corresponds to a 768 setting according to the thread listed here.

http://forums.sagetv.com/forums/show...ease+java+heap

100h=256
200h=512
300h=768
400h=1024

Last night I changed it to "400" = 1024MB, but couldn't reboot everything as recordings were in progress.

If I go to "Info" on either an extender or at the PC server, hould the JVM Heap size always match?

For several weeks, I noticed they were different, even after upping to "300"=768. Then last night with when checking it at both locations, they were both showing 400MB max which I presume to be equivalent to a setting of 200 in the registry? But when checking the registry value, it was 300h=768.

Strange. I'll reboot tonight and see what the changes are.

What drew my attention to this was that I installed the plugin for monitoring the Java Heap, and noticed after raising the value that the bar indicator showed really high usage still.

[jorton]

Originally Posted by hackzaw

Thanks for the response. When I reference the "300", I was indicating that was the setting I entered was "300" hex which corresponds to a 768 setting according to the thread listed here.

http://forums.sagetv.com/forums/show...ease+java+heap

100h=256
200h=512
300h=768
400h=1024

Last night I changed it to "400" = 1024MB, but couldn't reboot everything as recordings were in progress.

If I go to "Info" on either an extender or at the PC server, hould the JVM Heap size always match?

For several weeks, I noticed they were different, even after upping to "300"=768. Then last night with when checking it at both locations, they were both showing 400MB max which I presume to be equivalent to a setting of 200 in the registry? But when checking the registry value, it was 300h=768.

Strange. I'll reboot tonight and see what the changes are.

What drew my attention to this was that I installed the plugin for monitoring the Java Heap, and noticed after raising the value that the bar indicator showed really high usage still.

I don't think your reg setting is taking at all. Did you catch Razrsharpe's post about UAC in that thread? You may need to set the amount in the appropriate virtual store section of the registry if you haven't disabled it.

Cheers,

J

[gplasky]

If you haven't rebooted after changing the setting it is not going to take effect.

Gerry

[jorton]

I think he rebooted after setting to 768mb (original post) and it didn't take effect, so kind of looks like he doesn't have the right registry location.

J

[PLUCKYHD]

Pretty sure sagetv service needs to be off as well. You said it was recording so guessing you still had the service running as well.

[panteragstk]

Yep, registry changes won't take effect unless the application whose registry settings you are modifying has been restarted. I usually don't edit registry settings unless the app is closed.

[hackzaw]

I've changed the Java heap twice now.

The first time, I shut off the service, changed the registry to 300h=768, and even rebooted the computer and extender. When everything came back up, the PC Server showed JVM Heap Max = 400MB, but the extender showed JVM Heap Max = 700MB.

I just changed it again last night while the service was running to 400h=1024, but I know the changes wouldn't be reflected until I stop everything and restart (I'll just do a total reboot of the machine).

The weirdest part about all this was there up until last night, there was this discrepancy between PC and extender JVM heap sizes, with the setting at 300h=768 in the registry. But when I checked it last night, they were both showing 400MB max, and rechecking the registry setting, it still had 300h as the setting.

I'll report back tonight after I reboot everything. I'll make sure the registry setting is 400h=1024MB.

[hackzaw]

Alright - Problem seems solved!!

It had to do with changing the virtual registry as I guess I have UAC "on". Following Razrsharpe's suggested key change in the linked thread updated the heap accordingly (even without a Win7 reboot, but I did do a Sage7 reboot)

Thanks for the tips.

Side question - increasing this Java Heap should do what exactly? Should I see a performance increase? Less spinning circles? Faster display of fanart? No more Out of Memory errors?