Java Heap Size

[rickgillyon]

I've just been looking at my System Info in Sage. After a full system restart and no recordings, it shows that my Java Heap Size is 189/200. Is this likely to be a problem? Is it likely to cause delays waiting for free memory? I have 2GB, I'd be happy for Sage to grab more than 200MB if required.

(Don't know if it's related, but Sage became completely unresponsive when connecting with PS last night and I had to restart, when this happened in 6.0 beta it was an OutOfMemory error - I'm waiting to see if it recurs)

[flavius]

That does seem a bit high - do I read this correctly - this is a 10 tuner system?

[rickgillyon]

Originally Posted by flavius

That does seem a bit high - do I read this correctly - this is a 10 tuner system?

Yup!

[rickgillyon]

Just connected with PS again and had the same problem. Turned on debug logging now, so next time I should have more idea what's going on.

What happened to mandatory debug logging on betas?

No-one has any idea if the heap size could be causing this?

[flavius]

Originally Posted by rickgillyon

No-one has any idea if the heap size could be causing this?

Of course can the jvm heap size cause OutOfMemory exceptions. Sage could be following the paradigm of setting 'minimum=maximum size'

Or maybe not not. I would. Ideally you size the jvm heap just right.
I remember a few years ago Snapstream made a lot of noise about their 'Medusa' poc. IIRC that was a six tuner system.

Did Sage ever test a 10 tuner rig? I'd file a bug report, if you haven't done so already.

[rickgillyon]

Surely, if I have a 10-tuner rig, Narflex *must* have more....

[jlindborg]

has there ever really been 10 things on the telly at the same time you actually wanted to record? I can't imagine... there's just not that much good TV!

[rickgillyon]

Originally Posted by jlindborg

has there ever really been 10 things on the telly at the same time you actually wanted to record? I can't imagine... there's just not that much good TV!

I agree. Seven out of ten recordings are by the kids: Drake & Josh, Horrid Henry, Sleepover Club, Loonatics, Futurama, Simpsons...luckily I can keep the HDD clear with auto-delete. But we all use it, so we need 10 tuners.

(Except my wife who still swears tape is the best medium...)

[rickgillyon]

An update on this - looks like I was running out of memory in the heap. There's an entry in the registry under HKLM\Software\Frey called "JVMMaxHeapSizeMB". I've set this to Hex 200 (512MB) and a lot of my problems have disappeared. It mainly seems to hover around the 279/338 (ish) now. Great stuff!

BTW, Sage told me that at 10 tuners I've equalled the record as far as they know. I guess I'll have to add a USB tuner to get the record...

[Ryand833]

Interesting, I've always had a slight delay on my 4 MVP's as well, but never thought anything of it.

I checked my JVM heap in Sage and sure enough, it said 189/200/200 -- so I bumped it up to 512. I'll have to wait and see if it makes a difference.

Thanks for the tip.

[hemicuda]

Originally Posted by rickgillyon

I've set this to Hex 200 (512MB) ...

Checked mine and it was "0". changed it to 512. we'll see what happens.

[Ryokurin]

it helps a little, I have a 5 tuner system and it does tend to make it a little bit more responsive after a few days, but I usually use it a a cue to reboot the system. If I don't I eventually get a crash due to windows running out of virtual memory. I'm hoping that when I move to a server/client system it goes away.

[clayginn]

Mine was already set to (512) and don't think I changed it.

[John@TunerUK]

My GUI seems to be hesitating a lot currently. It will do what you want if you wait a while, but this can sometimes take up to 60 seconds!
It seems to be worse when navigating in or out of SageTV Recordings.
My figures aren't as high as those above, but they're not far away.
After a restart and about 20 min's use mine shows 147/200/200
Since I have plenty of memory spare I was going to try this to see if it helped.

Using regedit32 I have found HKEY_LOCAL_MACHINE\SOFTWARE\Frey Technologies\Sage TV\JVMMaxHeapSizeMB

Double clicking gives me a box entitled "Edit DWORD Value"
Value data : 0
Base : Hexadecimal (this is Selected) or Decimal (this is Unselected)

Is this the correct box to alter? And if so, should I enter 200 as the Value Data also?

Cheers

John

[brewston]

200 (Hex) = 512 (Dec) - so the radio button lets you choose which units to use, then set the data value to the appropriate value

Tim

[John@TunerUK]

Thanks for that
I've altered it, and it's showing up correctly (well 533Mb, close enough).
I'll see how it fairs after a few days use

[djseto]

I am running 6.3.5 and when I changed the registry to 512MB and I look at the JVM Heap in SageTV, it says 51/59MB. Shouldnt it say 51/512 or whatever its using vs. the max (512)?

I have been having a ton of problems with my HD Extender and I am wondering if its related to this. If I pull open task manager, SageTV is using on avg. 200MB of memory

[John@TunerUK]

There should be 3 numbers not 2, and the last one is your maximum available according to the registry setting.
It isn't worded very well in sage, but I presume it's layed out like this:-
Current ammount being used/Maximum that has been used/Maximum ammount settings will allow

You also have to restart the server software before any changes take effect

[djseto]

I changed back to the default theme and it now shows 3 numbers, that last being the maximum (533). For some reason the numbers shown are drastically different than the SageMC theme.

[brewston]

Could be a font thing ?