#(MauricioOf) PlayerUpdateTask high CPU usage

61 messages · Page 1 of 1 (latest)

ruby sigilBOT
#

(MauricioOf) PlayerUpdateTask high CPU usage

#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

marble pawn
#

!timings

narrow steepleBOT
# marble pawn !timings
Info: timings

The "timings" system within Spigot/Paper is incredibly inaccurate for use with Citizens, and cannot be used to diagnose any issues related to Citizens. It notably blames Citizens for a significant amount of entity-related lag (that isn't in any way caused by Citizens).

For accurate timings, you need a Java profiler. There are a variety of profiler options (WarmRoast, YourKit, VisualVM, ...), but the simplest to use on a Spigot server is a plugin named "Spark" that embeds WarmRoast, which you can find here: https://www.spigotmc.org/resources/spark.57242/.

To get a spark report, type /spark sampler, then replicate lag issues (for no more than about a minute), then /spark sampler --stop, and post the link it gives you.

marble pawn
#

!logs

narrow steepleBOT
# marble pawn !logs
Info: logs

Please post your full latest log file.

Background Info: One of the most helpful tools to identifying the source of a problem is your server logs file! Logs contain all sorts of important information like server and plugin versions, any error messages, and a lot more important information (More Info).

How To: Your log can be found in the logs folder within your server folder. The most recent log is a text file labeled latest.log. To get help using these logs, please open that file in a text editor and copy all of the text, then open https://paste.denizenscript.com/New/Log and paste the text into the box on the page. Then click "Submit" and copy the URL and paste that back into this channel.

Please do not upload the file to Discord or to other pastebin services, use the log pastebin linked above.

marble pawn
#

!spark

narrow steepleBOT
# marble pawn !spark
Info: spark

The "timings" system within Spigot/Paper is incredibly inaccurate for use with Citizens, and cannot be used to diagnose any issues related to Citizens. It notably blames Citizens for a significant amount of entity-related lag (that isn't in any way caused by Citizens).

For accurate timings, you need a Java profiler. There are a variety of profiler options (WarmRoast, YourKit, VisualVM, ...), but the simplest to use on a Spigot server is a plugin named "Spark" that embeds WarmRoast, which you can find here: https://www.spigotmc.org/resources/spark.57242/.

To get a spark report, type /spark sampler, then replicate lag issues (for no more than about a minute), then /spark sampler --stop, and post the link it gives you.

last widget
#

update-rate: 1s or update-path-rate: 1s ?

#

if I set it to more seconds, will that work?

jolly umbra
last widget
#

is a bedwars server do you still support 1.12.2?

jolly umbra
#

Using 1.12.2 is a bad idea regardless of what your server is, but yes, there is limited support

#

Updating to a recent version is strongly recommended, though

last widget
#

normally bedwars servers are 1.8.8 or 1.12.2, I have never seen a bedwars on 1.19.4

last widget
#

my other servers are at 1.19.4 rest assured, only bedwars will be 1.8 or 1.12.2

jolly umbra
#

It being bedwars shouldn't have anything to do with it

#

You can easily allow older versions to join if you want to

jolly umbra
last widget
#

well mush is giant and is 1.8, hypixel too

jolly umbra
#

Timings is inaccurate for Citizens specifically (and in general, Paper is planning on replacing it), should provide a spark report

last widget
#

no /timings paste?

jolly umbra
#

Using these ancient versions is a massive security risk, and there's really no reason to be doing that as you can easily let older versions join and restore old PVP if you want to

last widget
jolly umbra
last widget
#

finally sorry for the inconvenience and thank you

jolly umbra
#

Like, unless you have an actual reason to be using a version from several years ago, you should really update :p - we're happy to help with that in #1027976885520584814 if you'd like

#

Either way, no worries :D - if this is resolved then

past mossBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@last widget

last widget
#

it seems that the problem is back to 26%, I can't even log into the server and it looks like this

#

I will download spark if it is better for you

jolly umbra
#

As that info box/Paper mentions, Timings is just outright wrong sometimes, especially about Citizens

#

So yeah, need a spark report

last widget
#

ok

#

there are no players online and look at the CPU

#

86% CPU '-'

jolly umbra
#

Based on that log your server doesn't seem to be lagging at all, it's spending most of it's tick time sleeping (I.e. has nothing to do) - as you can see the TPS is basically 20 as well

#

Are you experiencing any actual lag?

last widget
#

I'm noticing only the tps like this when it is 1.12.2 and the tps should be 20.20.20 with 0 players

#

I will test recommend the Citizens

#

without the plugin

pliant storm
#

Need a spark profile when slowdown is happening this doesn’t show any slowdown

past mossBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@last widget

#

@last widget

Thread Close Blocked

Thread was closed either automatically by timeout or by the Discord manual close button. If closing was intentional, please use </resolved:1028673926114594866> or </invalid:1028673926898909185>.

#
Resolved

Thread closed as resolved.

#
Thread Reopened

Thread was manually reopened by @last widget.

#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@last widget