Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@cad435 RAM Issues #1

Open
mindforger opened this issue Jun 14, 2016 · 7 comments
Open

@cad435 RAM Issues #1

mindforger opened this issue Jun 14, 2016 · 7 comments

Comments

@mindforger
Copy link
Owner

mindforger commented Jun 14, 2016

@cad435 hope you get the notice :)

i was referring to the architecture of how the RAM in the JVM is organized

JAVA organized the RAM in different sized spaces for different aged data ... the default design ist capable to work optiomized for applications about 2GB in size and a mix of a buch of permanent data and a failry small amount of short life data .... what you need is an optimization for large amounts of short living data without killing the required space for long living data ... i can share my parameters when i am back home, so please be patient :)

@cad435
Copy link

cad435 commented Jun 14, 2016

allright, I'll try it, thanks in advantage!

@mindforger
Copy link
Owner Author

mindforger commented Jun 14, 2016

-XX:SurvivorRatio=3 -XX:+UseCompressedOops -XX:+AggressiveOpts -XX:+CMSScavengeBeforeRemark -Xms3G -Xmx4G -XX:NewSize=1G -d64 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSIncrementalMode -XX:GCTimeRatio=10 -XX:CMSInitiatingOccupancyFraction=70 -XX:CMSIncrementalSafetyFactor=70 -XX:+CMSClassUnloadingEnabled -XX:+DisableExplicitGC
Edit: forgot the most important tuning feature -XX:MaxTenuringThreshold=4

when your engage stuttering with high frequency turn this to 5 or 6 maybe even 7, but you will increase the total time of lag but reduce the frequency and the sensitvity to load :)

this will start witth 3Gig and max out at 4Gig but i'd prefere to upgrade it to at least 6Gig
NewSize=1G tells to use 1Gig of this space soley for short lifetime stuff and leave the rest to long life data

other than that it will use an alternative strategy for GC with less heavy but more often GCing increasing the GC rate when ever needed

it will warn you some of the methodes are deprecated but yet still functional and really worth it imho :)

@cad435
Copy link

cad435 commented Jun 14, 2016

Thx!

Apply as Global VM arguments or as start Args for minecraft?

@mindforger
Copy link
Owner Author

mindforger commented Jun 14, 2016

jvm arguments in the launcher, the RAM parameters may clash with the FTB settings, you can remove XMs XMn and XMx

@cad435
Copy link

cad435 commented Jun 14, 2016

I don't play FTB^^

I tweaked the whole setup today, I'm now not able to reproduce the lagg-error anymore, but I can't say if its the Args. or something else.

Anyway, I think shaders are running little more smooth, Thank You!

@mindforger
Copy link
Owner Author

mindforger commented Jul 4, 2016

@xannor default JRE is designed to handle up to 2GB or RAM everything beyond is a mess with it's GC style, read further in my original issue about that, you will be surprised

@mindforger
Copy link
Owner Author

mindforger commented Oct 7, 2016

@xannor and @cad435
you are welcome to update your command lines with my new explanations :D
i had some enlightment to some of the parameters and made a more or less condensed explanation
just watch my other issue #3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants