Performance tuning

Defaults are tuned to your server at install time and suit most people. Come here if reports feel slow, or if you’ve resized the server.

Settings → Performance

Setting	What it does
Analytics cache	How long a report is reused before being recalculated
Click log cache	The same, for the click log
Unique visit window	How long before a returning visitor counts as new
Unique lander click window	The same, for lander CTA clicks
Retry failed row loads	Retry a row that fails to load in a report

Cache settings

The trade is freshness against speed. A longer cache makes reports you open repeatedly feel instant; a shorter one shows new clicks sooner.

Raise it when you’re deep in optimisation, opening the same report over and over, and don’t need second-by-second numbers. Lower it when you’re watching a launch live.

Changing a filter or a date range always recalculates, so you’re never looking at stale numbers for a report you just changed.

Uniqueness windows

These decide when a returning visitor stops counting as a repeat and counts as new. See Metrics & counting rules for how that flows into your reports.

Changes apply from that moment on and don’t rewrite history, so a change mid-day makes that day inconsistent either side of it.

After resizing your server

Settings → Performance → Retune.

Your tracker’s resource settings were calculated from the CPU and memory the server had when you installed it. Resizing the droplet doesn’t update them, so a server upgraded from 4 GB to 16 GB keeps behaving like a 4 GB one and never touches the extra memory.

Retune re-reads the current hardware and rewrites those settings. It restarts part of the stack, so expect a short interruption.

Run it after any resize. Downsizing without it is the worse direction — the tracker keeps reaching for memory that no longer exists.

If reports feel slow

Work through these in order:

1. Narrow the date range. A full year grouped by hour is a lot of buckets. Check whether it’s slow generally or only on big ranges.
2. Retune, if you’ve ever resized the server.
3. Raise the analytics cache if you’re re-running the same heavy report repeatedly.
4. Still slow? Message @roitrack. Say which report, which date range, and how long it takes.

Disk space is worth watching

Click history grows steadily and it’s the thing most likely to fill your server. Your provider’s dashboard shows disk usage.

If you’re above about 80%, get in touch before it becomes urgent — a full disk slows everything down and is much easier to deal with early.

Sizing

The 2 vCPU / 4 GB minimum runs everything, but it’s the floor rather than a recommendation. The first symptom of an undersized server is slow reports, not lost clicks — tracking holds up long after the dashboard starts dragging.

Consistently above a few hundred thousand clicks a day, more memory helps more than more cores. Retune after any change.