![]() ![]() You might be curious what happens if you don't set the memory allocation flags at all. Setting the minimum and maximum as the same value sets the heap size to a fixed value which helps avoid performance hits as Java dynamically adjusts the heap size. You may have noticed that we're not specifying a range, like 512M to 2048M in our commands, but using the same value for the minimum and maximum heap size. If we want to increase the RAM allocation to, say, 2GB, you can simply shut down the server and run it again with increased values: java -Xmx2048M -Xms2048M -jar server. You can take the GUI flag off if you want a GUI window with performance stats, a player list, and a live view of the server log. Portion simply points Java's jar archive tool at the server file, and the noguiįlag stops the server from creating a GUI window. In the above command, we call on Java, we specify a starting heap size of 1024M and a maximum heap size of 1024M. Let's look at an example startup command and break down all the pieces. You can use either megabyte or gigabyte designations like 1024M or 1G with the flags. Which specify the maximum and initial heap size, respectively. ![]() ![]() You set the size of the heap, or memory allocation, with the flags -Xmx Instead, RAM allocation is handled by command-line arguments passed along to the server software during startup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |