#Suggestion for the Discord Adding to
1 messages · Page 1 of 1 (latest)
im confused on what this would do vs the normal command
like wouldnt the normal one just show more info
Not necessary, cause the spark profiler ends up showing an average of the results over all the ticks sampled
And a problem with averages is that could hide data outliers
Which tend to be the lag spickes
At least that is what I've gather from what I've read
should i just replace the old command then
I didn't suggest that because some may be used to a troubleshooting workflow with those types of results
The lag spikes guide from Spark also recommends the --only-ticks-over option to find the spikes https://spark.lucko.me/docs/guides/Finding-lag-spikes
https://github.com/etil2jz/etil-minecraft-flags
If lag persists, do the following command ingame:
/spark profiler --interval 100
Then, send the link in this channel.
oh wait
yeah because using --only-ticks-over will help catch actually probably laggy things
iirc interval also causes a delay
at least assuming i understand how interval works
The definition is "/spark profiler start --interval <milliseconds> to start the profiler and sample at the given interval (default is 4)" but not 100% sure what it means
that sounds like a delay
I think its just a delay
the current command isn't bad
but i do think --only-ticks-over is better
- no delay so it can possibly catch more info
- removes all the definitely not laggy stuff, its not like we look at it anyways, mostly we open up the largest cpu time and check that
!tps