Spark profiles Report help Before vs after

Get better reports from better captures.

Use this guide to upload the right files, read the important sections first, and compare fixes without guessing your way through server performance.

Uploads

Send useful diagnostics.

Spark profiles are best for performance triage. Latest logs, crash reports, debug logs, JSON, text files, and zipped diagnostic bundles can help too.

.sparkprofile.log.txt.json.zip
Upload file
Reports

Start with the summary.

Read the plain-English summary, grade, top systems, top mods, and likely causes before digging into raw hotspots.

View reports
Safety

Keep secrets out.

Do not upload private keys, payment exports, passwords, tokens, database dumps, or unrelated personal data.

Check before upload
Best practice

Capture before and after.

Capture one profile during real load, apply one fix, then capture again. Comparison only helps when the test is clean.

Profile during load

Capture while the server is doing real work.

Before
Apply one fix

Change one thing so the result means something.

Fix
Upload again

Compare grade, MSPT, TPS, and recommendations.

After
FAQ

Common questions

What file should I upload first?

Use a Spark profile captured while the issue is happening. If the problem is lag, tick time, or low TPS, this is usually the most useful starting point.

Does AI replace the report?

No. AI is an optional explanation layer built from TickVisor's parsed report data. The normal report still works without AI credits.

Why compare two reports?

Comparison shows whether a change improved or worsened the server instead of relying on vibes, the worst metric ever invented.

When should I upload logs?

Upload logs when the profile alone does not explain a crash, startup failure, warning spam, or mod-specific error.