Java Heap question

[Evil_Attorney]

Dumb question, but I just upgraded to v9 from v7. In v7, I had changed the registry entry for the Java heap to increase it to 1024, I believe. I used the windows installer to install v9. Do I need to change anything back in the registry?

[Fuzzy]

I believe the registry setting would be preserved. You can check your heap size in sage's System Information screen.

[Evil_Attorney]

Hmm...it is 779. I guess I need to change it back to 1024. Is that still the highest it can go? I thought I remember reading that v9 could take advantage of more Java memory somehow.

[Evil_Attorney]

Weird, my registry entry does say 1024 already. It apparently isn't getting recognized.

[Evil_Attorney]

Ok, I deleted the java heap registry entry, restarted Sage, it added the entry back with a "0" value. I shut down Sage, set the value to 400, but, Sage is still showing 779. Sage does not seem to be apply the 1024 java heap entry.

[nyplayer]

There might be more than one entry. do a find on JVMMaxHeapSizeMB in the registry and do a refind until you get to the end of the registry.

Someone else had this problem.

https://forums.sagetv.com/forums/sho...67&postcount=2

[Evil_Attorney]

Thanks, yea, I saw that thread and already tried searching for other registry entries, but only the single entry was found in my registry.

[jusjoken]

Change the registry and then start sage with admin and see if it then keeps that setting.

You may need to change the permissions in the Frey area to "everyone" with full access and cascade it to its children to solve this.

k

[Evil_Attorney]

Thanks. The Frey registry area was already set to "full control" for "everyone". I am running the Sage service as an administrator (so that I can access network shares properly). Sage seems to access this registry area, since if I delete the Java registry entry completely, the Sage service adds it back with a "0" value upon starting. When the registry is set to 400, Sage doesn't change that value. It just doesn't seem to apply it to its settings. Since I upgraded from v7, is there another setting in the Sage properties or somewhere else that might need to be changed?

[willieb]

Originally Posted by Evil_Attorney

Thanks. The Frey registry area was already set to "full control" for "everyone". I am running the Sage service as an administrator (so that I can access network shares properly). Sage seems to access this registry area, since if I delete the Java registry entry completely, the Sage service adds it back with a "0" value upon starting. When the registry is set to 400, Sage doesn't change that value. It just doesn't seem to apply it to its settings. Since I upgraded from v7, is there another setting in the Sage properties or somewhere else that might need to be changed?

Hmmmmm. I'm at 779 too and I know I went up to 1024 years ago. That might explain the increased frequency of the spinning circle I have seen with version 9. Will have to see if I can increase on Saturday. I will let you know if it "takes" for me. If you figure it out please post the solution. Thanks.

[wayner]

Originally Posted by Evil_Attorney

Hmm...it is 779. I guess I need to change it back to 1024. Is that still the highest it can go? I thought I remember reading that v9 could take advantage of more Java memory somehow.

This is only true of the Linux version of SageTV as it was rewritten for the 64 bit version of Java. No one has had a chance to do that for Windows yet. This is the main reason why I am switching to a Linux/unRAID server.

[SDeGonge]

Originally Posted by willieb

Hmmmmm. I'm at 779 too and I know I went up to 1024 years ago. That might explain the increased frequency of the spinning circle I have seen with version 9. Will have to see if I can increase on Saturday. I will let you know if it "takes" for me. If you figure it out please post the solution. Thanks.

Same here, 779. Since I upgraded to V9 I've been hitting my warning level on a daily basis. Let us know if you can get it back up to 1024.

[Evil_Attorney]

Maybe we should flip this around first. Has anyone been able to get 1024 on v9 in Windows?

[EnterNoEscape]

Originally Posted by Evil_Attorney

Maybe we should flip this around first. Has anyone been able to get 1024 on v9 in Windows?

I double checked my old production Windows SageTV install and it was definitely using 1024. I upgraded it to the latest v9 version and it's still using 1024.

[wayner]

My Sage V9 on Win10 report 1038MB. The registry is set at 0400 hex or 1024.

[Evil_Attorney]

Strange. Maybe it has something to do with mine being an upgraded version from v7?

[Fuzzy]

How did you upgrade to v9. You might try doing a repair with the installer.

[willieb]

Originally Posted by Evil_Attorney

Maybe we should flip this around first. Has anyone been able to get 1024 on v9 in Windows?

Ok, I was able to increase my heap size and it seems to have stuck. I used the SageTV Registry Settings program that I downloaded from babgvant's web site. You can google it. I set mine at 1280. Right now I am showing max of 1297. I'll let you know if somehow it reverts.

[wayner]

In the past people have had issues setting it to larger than 1024 or 0400hex. This is the reason why I moved to Linux were the sky is the limit as I demonstrated here: https://forums.sagetv.com/forums/showthread.php?t=64017

[SDeGonge]

No luck here....

Windows 10 64bit
SageTV V9
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV\JVMMaxHeapSizeMB is set to 400h (1024)

Rebooted
SageTV still reports 779MB