You are also giving your entire 8GB of RAM to Java (or more specifically, the JVM heap). Not a good idea since your system itself needs some RAM to operate. If Java tries to use all of that your system will start paging RAM to storage, and that will kill performance.
That tells Java it can have 2GB initially, but can use up to 4GB if needed.
Note that the JVM uses more memory than just the heap. For example Java methods, thread stacks and native handles are allocated in memory separate from the heap, as well as JVM internal data structures. So you really don't want to allocate all of your RAM to the Java heap.
In 1.13 it takes me a very long time to destroy blocks because they keep reappearing. Anyone know a fix for this?
Are you playing on a server?
If so, then that's server lag. If not, then your system may be too slow for 1.13.
I am not playing on a server, but I have 8GB RAM and a GTX 770m which I thought would be enough
Post a screenshot with F3 enabled and your JVM arguments.
Here they are, thank you!
Well if you see that your system is struggling with lag, wouldn't it be a good idea to turn some settings down, like the render distance?
Oh I didn't see that my render distance was all the way up... Thank you it solved the problem!
You are also giving your entire 8GB of RAM to Java (or more specifically, the JVM heap). Not a good idea since your system itself needs some RAM to operate. If Java tries to use all of that your system will start paging RAM to storage, and that will kill performance.
Try something like:
That tells Java it can have 2GB initially, but can use up to 4GB if needed.
Note that the JVM uses more memory than just the heap. For example Java methods, thread stacks and native handles are allocated in memory separate from the heap, as well as JVM internal data structures. So you really don't want to allocate all of your RAM to the Java heap.
That should be more than enough. But do adjust your memory allocations.
Ok! Thank you very much for the help!