Compare two spark profiles under the same Minecraft workload

Applies to: spark; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A quieter server often looks faster regardless of the configuration change. A fair spark comparison repeats the same workload and reports the conditions beside the result. This prevents a maintenance change from receiving credit for an empty player list.

Record the starting point

Choose one measurable complaint, such as a pause when entering a prepared area. Record the server build, plugin versions, player count and approximate activity. Keep the previous configuration and decide what improvement would be noticeable before changing anything.

Work through the change

Capture a bounded baseline while repeating the chosen action. Note the time window and whether chunks are already generated or need generation.
Apply one candidate change on a controlled service copy or planned maintenance window. Avoid combining view-distance, plugin and world-generation changes in one comparison.
Capture the same duration with comparable players, route and chunk state. Use the same profiler mode and slow-tick threshold if one was selected.
Compare tick measurements and the relevant call branches, not just the largest percentage. Record any difference in workload that could explain the result independently.

Check the result

A credible result links the changed setting to an observable improvement under similar conditions. Keep both captures and the exact change. If the second test benefits from warmed caches or generated chunks, state that limitation and repeat an equivalent baseline before drawing a stronger conclusion.

If the result differs

If overall percentages shift but tick duration stays similar, the change may have redistributed sampled work without fixing the player's complaint. If the trigger did not occur in one capture, the pair is not a valid comparison. Gather a smaller repeatable test instead.

Restore the previous setting if the change harms gameplay or does not address the measured symptom. Preserve both reports as evidence rather than keeping an unproven tweak permanently. No world reset or player-data removal is part of a profile comparison.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report