spark

spark

Mods
118M Downloads

Profiler argument `--only-ticks-over` is unreliable

Miasmusa opened this issue ยท 0 comments

commented

Description

Basically identical to #411, I initiated the profiler with --only-ticks-over 500, but the profile does not seem to indicate that the filtering was successful. However, after more testing, it seems that the option only reliably does not work when --thread is set to *. I also recall failures without --thread set, but I haven't been able to replicate it.

Reproduction Steps

  1. Run spark with the --only-ticks-over and --thread * arguments
  2. Run spark without said arguments
  3. View resulting profiles, notice reported data is similar in both profiles

Expected Behaviour

Always display only ticks longer than set in --only-ticks-over, or issue a warning if current settings are incompatible.

Platform Information

  • Minecraft Version: 1.21.1
  • Platform Type: client
  • Platform Brand: Fabric
  • Platform Version: 0.16.10

Spark Version

1.10.109

Logs and Configs

No response

Extra Details

Success: https://spark.lucko.me/KBWWhSrMjc
Failure despite frequent spikes and interval set at 1, possibly due to --thread *: https://spark.lucko.me/H9FIzZKwB7
Reporting no data, despite me seeing a 500 ms+ tick in the tps graph: https://spark.lucko.me/SoqNKHn0Hm

In game tps graph for an idea of what kind of lagging I'm seeing:

Image