Description

When I try to do a /spark profiler start --only-ticks-over 300, it's impossible to get accurate data. Spark always causes lag spikes when using this combined with /spark tickmonitor

Reproduction Steps

A server with already have cpu usage (3 year old map, 200 players online), start a spark tick monitor along with a sampler of ticks over 300.

Expected Behaviour

Spark should not show up on the sampler... right?

Platform Information

• Minecraft Version: 1.20.1
• Platform Type: Server
• Platform Brand: Pufferfish fork

Spark Version

1.10.55

Logs and Configs

{
"_header": "spark configuration file - https://spark.lucko.me/docs/Configuration",
"backgroundProfiler": false
}

Extra Details

Makes it hard to find lag spikes when spark is always #1 result