java paramaters for 1.7.10

[Liquid Klone]

I am playing impactflux for 1.7.10 currently because the hqm is amazing in this pack also, learning the new thermal expansion is fun and being forced to try other pipes is cool too. using @Eyamaz old java paramaters post worked well for 1.6.4, but it seems that i get much better fps with these paramaters, however my tps is horrible, especilly when mining. I notice that my used memory rarely goes above 12% before it goes back down to 9. it then quickly goes back up again. I dont know much about java,but I suspect something is causing garbage disposal to be overly active, causing necessary ram to be unnecessarily dumped. anyone know how I might be able to make this better? I added fastcraft to the modpack, if that is relevant.

-Xmx6G -Xms6G -Xmn2048m -XX:+DisableExplicitGC -
XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+UseNUMA -XX:+CMSParallelRemarkEnabled -XX:MaxTenuringThreshold=15 -XX:MaxGCPauseMillis=30 -XX:GCPauseIntervalMillis=150 -XX:+UseAdaptiveGCBoundary -XX:-UseGCOverheadLimit -XX:+UseBiasedLocking -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -XX:+UseFastAccessorMethods -XX:+UseCompressedOops -XX:+OptimizeStringConcat -XX:+AggressiveOpts -XX:ReservedCodeCacheSize=2048m -XX:+UseCodeCacheFlushing -XX:SoftRefLRUPolicyMSPerMB=20000 -XX:ParallelGCThreads=10

 

[twisto51]

This is going to sound funny but I found simply removing all of the extra parameters I was using to make 1.6.4 run better made 1.7.10 run better.

 

[b0bst3r]

This is going to sound funny but I found simply removing all of the extra parameters I was using to make 1.6.4 run better made 1.7.10 run better.

Funnily enough I did the same with the same outcome.

 

[Omicron]

I notice that my used memory rarely goes above 12% before it goes back down to 9. it then quickly goes back up again. I dont know much about java,but I suspect something is causing garbage disposal to be overly active, causing necessary ram to be unnecessarily dumped. anyone know how I might be able to make this better?

For starters, assign less memory. If you're in singleplayer, try 1.5GB max. A client connecting to a server can almost always get away with 1GB just fine. I recommend only raising this (in 0.5GB increments) if you get an actual heap space crash. Want to see how that feels and how the crashlog looks? Load up vanilla 1.8 completely without java arguments, switch to 32chunkcs view distance, and try to let it load all chunks in all directions from where you're standing. You will clearly see the memory tracker in the F3 panel fill up to maximum near the end of it, followed by a freeze and crash shortly after because the Minecraft default 1GB heap space can't handle it. With 1.5GB this problem no longer occurs.

Reason being: if you tell Java to take 6GB, then Java takes 6GB. It doesn't matter if your actual memory usage hovers around 10% of that as you described... it still uses 6GB because you explicitly told it so. And that entire 6GB space is going to get managed and checked and garbage collected constantly. The more you assign, the more CPU time you invest in uneccessary overhead, and therefore the less CPU time is left for your game to do its world tick.


But the advice from twisto and b0bst3r is also sound - Minecraft 1.7 is just a completely different beast that nobody has really analyzed yet to the degree Eyamaz analyzed 1.6, and as always with Java arguments, the chance of making things worse is much higher than making things better if you just set things without fully understanding what they do. Just give it a whirl without arguments and see how things pan out?