Spigot 1.9.4 TPS issue

Discussion in 'Spigot Help' started by melodicaxe, May 31, 2016.

  1. Hi, I am running a spigot server on my dedicated machine with the following specs:

    Intel Xeon CPU E5-1630 v3 @ 3.70GHz 3.70GHz
    64 GB RAM
    1TB SSD

    I notice that I never get 20 TPS which I am fine with even when I am the only player on the server, however I some times get TPS drops to 18 which are sudden and can cause that skip lag feeling. Anyway here is my timings report https://timings.spigotmc.org/?url=16872555

    Looks like world save is the biggest issue, could someone guide me what the world save event actually means and how can I reduce its load. The map is 80GB.
     
  2. It might be autosave. Bukkit has a build in autosave feature. Disable it if it's not important. You could also disable the save structure information (is in multiple config files!) But it's not a recommended option.
     
  3. 0.92% 5,629.76% 16.89 s 2,814.88 ms 0.0 0.0k World Save

    Im sure its world save, due to that ^
     
  4. Ok what does this mean, here is my current spigot config:

    server-properties http://pastebin.com/eXjrSjUi
    spigot http://pastebin.com/rdPmeQsN

    And more importantly what can I do to fix this?
     
  5. In the bukkit.yml you can turn the autosave off by setting it to 0 I think. Then it doesn't try to save the world anymore. Maybe that works
     
  6. But why is this happening is my map too big??

    I dont want to risk any data loss by turning this feature off. Is spigot incapable of saving a map.
     
  7. It's not, but saving a map requires the data being saved to a storage device. And this can be slow, if there are a lot of chunks loaded and changed then it needs to save a lot of chunks, it also needs to save special blocks with special data and entities with special data and having a huge world doesn't slow it down, but spigot has more work to do, making it take longer overall. Turning autosave off means that the world isn't saved every x ticks, but it still saves the world when shutting down the server. So if the server can suddenly crash, then the world is back to when the server started up for the last time. If you want something like a daily backup, you could schedule a server restart that happens every day. This should work, IF YOU CAN schedule server restarts, for example with MultiCraft you can schedule stuff.

    You can also make the server save a world with the command /save-all This can be really useful.
    Something that you might be smart to do, is to do that save command and see if the lag spike appears, if so you know that it's definitely the world save.

    I would say that if it's not a huge problem that you might loose a days work in case of a server crash, then turning autosave off can be good, then you can see if the lag disappears and if it doesn't, or you get problems with the world being set back, then it might be good to turn autosave on again
     
    • Agree Agree x 1