Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

TPS drops despite low CPU usage


misikokos1
 Share

Recommended Posts

Click on your link.

See where it says "all" - click on it and it will change to "flat".

Now click the arrow next to "Server Thread 100%" at the bottom.

You will get something like the following:

Quote

Server thread100.00%

net.minecraft.server.MinecraftServer.func_240802_v_()99.86%

net.minecraft.server.MinecraftServer.func_240783_a_()99.86%

net.minecraft.server.MinecraftServer$$Lambda$10803.658110002.run()99.86%

java.lang.Thread.run()99.86%

net.minecraft.server.MinecraftServer.tick()98.23%

net.minecraft.server.MinecraftServer.updateTimeLightAndEntities()98.13%

net.minecraft.server.dedicated.DedicatedServer.updateTimeLightAndEntities()98.13%

net.minecraft.world.server.ServerWorld.tick()92.00%

net.minecraft.entity.LivingEntity.tick()83.77%

This says your server thread is spending ~84% of its time ticking entities.

 

Now click where it says "flat" and it should change to "sources".

You should see something like the following:

Quote

alexsmobs (28881.13ms)

Server thread20.29%

dungeons_mobs (19509.26ms)

Server thread13.71%

projectvibrantjourneys (11128.12ms)

Server thread7.82%

untamedwilds (6517.9ms)

Server thread4.58%

survive (5553.77ms)

Server thread3.90%

rats (3953.77ms)

Server thread2.78%

So at least 34% is in alexmobs and dungeonmobs.

It will be more than this, since it is only counting where it is actually inside their code.

It does not include time spent by Minecraft handling the entity before it calls their code.

 

Things you can do include:

* Look at the mods documentation and talk to the mod author about optimisation these mods, e.g. changing mob caps to spawn less mobs

* Change the "simulation-distance" in server.properties so that the server can stop ticking mobs when they are closer to the player, the default is 10 chunks

 

Edited by warjort

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.