Linux 9.1.7 - VERY high java

[jt4242]

Sage Linux v9.1.7.581
Linux Mint 18 guest in Oracle vbox (8 GB RAM) within Windows 7x64 host, 32GB RAM
Java 1.8.0_151 memory set at 2048


Is anyone else seeing very high JVM heap size in linux, the v9 9.1.7.581 version?

I actually got two warnings last night - Java heap has exceeded warning level (heap size set at 2048). I have never had a warning in Linux before.

So I set up a bare installation of versions 9.1.7.581 and of 9.0.14 with no plugins and only 1 tuner.

In version 9.0.14 a typical memstat, shortly after starting, in Sagetv_0 .txt file is:
Used=103MB Total=152MB Max=1908MB
in 9.1.7
Used=592MB Total=1010MB Max=2147MB

Last night with my regular full setup going the stats were:
Used=1693MB Total=2136MB Max=2147MB

I'm attaching the two Sagetv_0.txt files from my testing with the basic setups and if anyone can see why I am having this problem, I would really appreciate it...sorry 1 file is zipped because it was too large.

Thanks so much,
Julie

[stuckless]

I looked at the MemStats in your .zip log file, and not showed it over 600mb out of the 2g that you set.

Originally Posted by jt4242

Sage Linux v9.1.7.581
Linux Mint 18 guest in Oracle vbox (8 GB RAM) within Windows 7x64 host, 32GB RAM
Java 1.8.0_151 memory set at 2048


Is anyone else seeing very high JVM heap size in linux, the v9 9.1.7.581 version?

I actually got two warnings last night - Java heap has exceeded warning level (heap size set at 2048). I have never had a warning in Linux before.

So I set up a bare installation of versions 9.1.7.581 and of 9.0.14 with no plugins and only 1 tuner.

In version 9.0.14 a typical memstat, shortly after starting, in Sagetv_0 .txt file is:
Used=103MB Total=152MB Max=1908MB
in 9.1.7
Used=592MB Total=1010MB Max=2147MB

Last night with my regular full setup going the stats were:
Used=1693MB Total=2136MB Max=2147MB

I'm attaching the two Sagetv_0.txt files from my testing with the basic setups and if anyone can see why I am having this problem, I would really appreciate it...sorry 1 file is zipped because it was too large.

Thanks so much,
Julie

[jt4242]

I know but SageTV was only on for 10 minutes, I had only 1 tuner installed and there were no plugins installed so, from what I had been used to, even 600MB seems high.

I don't have the .txt file from last night when I got the warnings. I guess my biggest concern was getting the warnings - it just has never happened to me with Linux.

I posted the two .txt files to also ask why memory seems to be handled so differently in each version. With 0.14, even now (I'm back on that version), the highest my usage has gotten after many hours is 330/353/1909 but with 9.17, those numbers were higher than 1693/2136/2147MB.

And, maybe this is a dumb question, but why, when the same amount of memory is allocated in both versions, the MAX in 0.14, shows as 1909 but as 2147 in v9.17?

I'll go back to 9.1.7 tonight and try to get a .txt file when it exceeds the limits.

[stuckless]

I did see some exceptions related to sdepg in the log that you posted. Not sure how that might impact stuff. It was looking like it was trying to download some images from schedules direct. Not sure of all the changes in this release. I'm running this release, and to be honest, I see my memory to be high, but it never affects my usage. Depending on what it's doing, java will keep allocating memory, and so, a 2g java will eventually fill up, and then it will keep recovering memory as needed. It's only an issue if you start getting java Out of Memory errors, which generally indicates a memory leak in the code.

[EnterNoEscape]

Originally Posted by stuckless

I did see some exceptions related to sdepg in the log that you posted. Not sure how that might impact stuff. It was looking like it was trying to download some images from schedules direct. Not sure of all the changes in this release. I'm running this release, and to be honest, I see my memory to be high, but it never affects my usage. Depending on what it's doing, java will keep allocating memory, and so, a 2g java will eventually fill up, and then it will keep recovering memory as needed. It's only an issue if you start getting java Out of Memory errors, which generally indicates a memory leak in the code.

If you don't see any warnings in the UI about EPG, it's a sign things are ok. Most of the SDEPG exceptions you'll see are related to getting headshots for celebrities and have no impact worth mentioning to either the heap size or the quality of the EPG data itself.

High heap usage is mostly because of how G1GC works. We could just stop using it completely, but like you stated, unless you actually see OOM errors, there isn't a problem.

[jt4242]

Thank you both. I'm glad to know that the high memory is not just me - though I do seem to be alone in getting out of memory errors. And reading about G1GC has been interesting.

So far no more errors but I'll keep watching and post if any occur - thank you again.