Ok guys, I have been having this issue for awhile now. I get a framerate drop from 75 to 35 around every 3 minutes.
I have tried all kinds of settings, including turning vsync on and off, changing in-game graphics to fast, and lowering mipmapping. I have put my specs in the image below. I also have 8G allocated to Minecraft. Anything lower and the lag spikes get more frequent.
Ok guys, I have been having this issue for awhile now. I get a framerate drop from 75 to 35 around every 3 minutes.
I also have 8G allocated to Minecraft. Anything lower and the lag spikes get more frequent.
Stop shooting yourself in the foot.
Less than 8G has more frequent lag spikes because it takes less time to totally consume and trigger a "stop the world" garbage collection cycle..
You have OBVIOUSLY changed Xmn DON'T DO THAT.
This has helped significantly. Thank you. I did change it. However, nowhere that I have read has said leave the Xmn alone. I was curious as to whether it had something to do with the Java Garbage collector or not. This makes a lot more sense now by the way it was behaving.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Ok guys, I have been having this issue for awhile now. I get a framerate drop from 75 to 35 around every 3 minutes.
I have tried all kinds of settings, including turning vsync on and off, changing in-game graphics to fast, and lowering mipmapping. I have put my specs in the image below. I also have 8G allocated to Minecraft. Anything lower and the lag spikes get more frequent.
Only allocate 1 gig of ram to minecraft unless you are using extremely high resolution resource packs and/or shaders.
Post your current JVM arguments.
It sounds like its the autosave. Download and install OptiFine, and turn down autosave times. See if it makes a difference.
Did you try unplugging and plugging it back in kappa
Stop shooting yourself in the foot.
Less than 8G has more frequent lag spikes because it takes less time to totally consume and trigger a "stop the world" garbage collection cycle..
You have OBVIOUSLY changed Xmn DON'T DO THAT.
This has helped significantly. Thank you. I did change it. However, nowhere that I have read has said leave the Xmn alone. I was curious as to whether it had something to do with the Java Garbage collector or not. This makes a lot more sense now by the way it was behaving.