Optifine is hit or miss as far as graphical issues go. Depends on graphic card and several other issues. I myself have gotten several graphical issues/crashes with optifine.[DOUBLEPOST=1405374539][/DOUBLEPOST]I don't run into any of these problems with optifine? What did you do to get these errors? I am on 1.6.4 64 bit java monster.
I just tried your test pack arguments. While I noticed no difference in FPS, my memory usage went down from 30% to a max of 10% in vanilla 1.7.10. Dayum.It's not that they arne't good, it's just that half of them don't do anything anymore.
I don't run FTB packs. But I do know that after some tweaking I got my test pack to run like a charm using J8, unfortunately OSX sucks and uninstalled it after the first restart. It should work fine, but Java 8 still isn't recommended, so it isn't recommended.
Personally, I write my own JVM arguments.
Here are the JVM arguments I use for all of java:
I use Java 7 update 60.Code:-XX:-DisableExplicitGC -XX:-RelaxAccessControlCheck -XX:MaxPermSize=128M -XX:MinHeapFreeRatio=30 -XX:+UseFastAccessorMethods -Xmn=2000M -Xmx=2000M
For a large pack I play I use:
Code:-XX:NewRatio=3 -XX:SurvivorRatio=3 -XX:TargetSurvivorRatio=80 -XX:MaxTenuringThreshold=8 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=10 -XX:GCPauseIntervalMillis=50 -XX:MaxGCMinorPauseMillis=7 -XX:+ExplicitGCInvokesConcurrent -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60 -XX:+BindGCTaskThreadsToCPUs -Xnoclassgc
For my test pack I use:
Code:-Xms512M -Xmx2048M -XX:PermSize=256m -XX:+UseLargePages -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -XX:+OptimizeStringConcat -XX:+UseBiasedLocking -Xincgc -XX:MaxGCPauseMillis=10 -XX:SoftRefLRUPolicyMSPerMB=10000 -XX:+CMSParallelRemarkEnabled -XX:ParallelGCThreads=10 -Djava.net.preferIPv4Stack=true
Yes, because they are, and I've told you this in one of our convos.
-XX:ReservedCodeCacheSize=256M -DJINTEGRA_NATIVE_MODE -DJINTEGRA_COINIT_VALUE=0 -Dsun.io.useCanonCaches=false -XX:ThreadPriorityPolicy=42 -XX:CompileThreshold=1500 -XX:+TieredCompilation -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -XX:+UseBiasedLocking -Xverify:none -XX:UseSSE=3 -XX:+OptimizeStringConcat -XX:+UseFastAccessorMethods -Xrs -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSIncrementalPacing -XX:+AggressiveOpts
Optifine is hit or miss as far as graphical issues go. Depends on graphic card and several other issues. I myself have gotten several graphical issues/crashes with optifine.
I decreased it to 3gb. Also, IIRC Java 8 has something that only garbage collects RAM that is being used (ie. if the Java app is only using 2gb out of 7gb, it just ignores the extra 5gb until something uses it), but I could just be remembering things that aren't real so don't get all upset if I'm wrong.Also never allocate 7 gigs of RAM as java garbage collection with that is real bad. I usually do 2 - 3.5 gigs of RAM 3.5 being absolute max
try it with 3 and see if you get improvement. I didn't know about java 8 having such (if you are correct)I decreased it to 3gb. Also, IIRC Java 8 has something that only garbage collects RAM that is being used (ie. if the Java app is only using 2gb out of 7gb, it just ignores the extra 5gb until something uses it), but I could just be remembering things that aren't real so don't get all upset if I'm wrong.
I tried everyone's arguments with 3gb, mine still performed best.try it with 3 and see if you get improvement. I didn't know about java 8 having such (if you are correct)
nothing about your args just in general. Like did you see an improvement with your JVM arguments with 3gbI tried everyone's arguments with 3gb, mine still performed best.
I have only tested them on 1.6.4Do those arguments (satanicsanta's) also apply for 1.6.4?
woah.Optifine is hit or miss as far as graphical issues go. Depends on graphic card and several other issues. I myself have gotten several graphical issues/crashes with optifine.[DOUBLEPOST=1405374539][/DOUBLEPOST]
I just tried your test pack arguments. While I noticed no difference in FPS, my memory usage went down from 30% to a max of 10% in vanilla 1.7.10. Dayum.
IIRC mine are taken directly from the Oracle site.People really need to stop spouting random JVM arguments unless they actually know what they are doing. A shit ton of the flags are all placebos or just call different flags.
IIRC mine are taken directly from the Oracle site.
They are listed on the first page...Can you be more specific? Oracle has documentation on every flag in existence, that doesn't mean they should be used.
This is what I am talking about. You obviously have a different meaning of first page.They are listed on the first page...
-Xms3G -Xmx3G -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+CMSClassUnloadingEnabled
http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.htmlThis is what I am talking about. You obviously have a different meaning of first page.
They are neither here: http://www.oracle.com/index.html
Nor are they here: http://www.oracle.com/technetwork/java/javase/downloads/index.html
Here are the JVM arguments I use for all of java: