#(vladyaso) lagg
64 messages · Page 1 of 1 (latest)
(vladyaso) lagg
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.
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 profiler start, then replicate lag issues (for no more than about a minute), then /spark profiler stop, and post the link it gives you.
^ grab a spark report and we can look over it for you
no
👍
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.)
@marble saddle
second
I can’t, there’s a dedicated server IP
rcon ip...
Can’t really help then 100%
Enable citizens debug
Find the npc on the chunk border
Move it off the chunk border
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.)
@marble saddle
!!!
Thread closed as resolved.
Thread was manually reopened by @marble saddle.
A little bit later
Citizens::Task: net.citizensnpcs.util.PlayerUpdateTask (interval:1
Timings is entirely inaccurate, especially for Citizens - there's a reason Paper themselves are planning on replacing it with spark
We'd love to help you with your issue, but without a spark report we're simply unable to ;-;
I am not able to send a link to spark, I can only use screens there
If all that's stopping you is that 1 setting in server.properties, just temporarily remove it before taking a report
But we can't really help with just screenshoots
Okay, I'll do it tomorrow then.
Can I send Spark to someone in a private message?
Hi
Why not posting it here?
Ok wait a couple of hours..
this spark shows you're running perfect tps and that the server isn't doing anything 85% of the time it was running
can you record a moment of lag?
can you send that spark report instead?
it doedsn[t reflect what you shared
205 is high, it would reference performance spikes
106.5 is low but it's not under heavy load
that or maybe consider either attempting or responding with if you've taken fullwalls suggestion please
15 min
There's still no lag
It's better to run a spark report when you receive lag for a short duration
1-2 minutes
Still,
^ please do the steps fullwall posted,
you can also upload the log file here
!pastelog
Help us help you by pasting your full server log directly to https://paste.denizenscript.com/New/Log (and not any other pastebin service) and linking it back here.
200 mspt could indicate potential lag spikes
Okay, it’s difficult for me, can I close this topic?
if you want to, sure.
if you want to try again later, you should ask exactly what you need to give us so we can help you understand next time
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.)
@marble saddle