Slow performance
Slowness can come from your place size (lots of scripts and instances to sync), the model choice (MAX is larger and slightly slower per token), peak-load queueing, or browser focus state. Here's how to diagnose each.
Symptom: AI responses feel slow
Response time depends on task complexity, model choice, and current server load. Here's the priority order to check:
Fix steps
- What model are you on? Revix MAX has a larger context window but is slightly slower per token than Standard. For straightforward tasks, Standard is faster.
- What plan are you on? Developer and Studio plans get priority queue access. Free users get deprioritized during peak hours. See credits and billing to upgrade.
- Is the task genuinely big? Refactoring 20 scripts is going to take longer than tweaking one function. Break large tasks into smaller messages.
- Are you in peak hours? Try again later, or upgrade for priority.
Symptom: large game, slow sync and slow AI inspection
If your place has 10,000+ instances or 100+ scripts, expect:
- Slower initial sync when the plugin first connects (more data to push)
- Slower AI tool calls that walk the script tree (more files to look at)
Fix steps
- The first sync after connecting is the worst — subsequent syncs are incremental and faster.
- When asking the AI to make changes, name the specific scripts or services it should look at instead of letting it scan everything: "edit the script at ServerScriptService.PlayerHandler" is much faster than "find the script that handles players."
- Move scripts you don't need synced into ServerStorage — Revix won't sync them, and the tree gets smaller. See scripts not syncing.
Symptom: Studio lags during sync
A small lag spike during the first sync after connecting is normal — the plugin is walking the entire script tree at once.
Fix steps
- Wait it out. After the first sync, subsequent syncs are smaller and barely noticeable.
- If Studio is consistently lagging on every sync, you may have something else going on — open View > Output and look for non-Revix warnings.
Symptom: dashboard feels stale when I tab back
Browsers throttle background tabs.
Fix steps
- Refocus the dashboard tab. Live streaming and updates resume as soon as the tab is active again.
- Resumable streaming means you didn't lose anything — the agent kept running on the server while you were away.
Symptom: lots of small messages feel sluggish vs one big one
Each message includes a setup overhead — context loading, tool wiring, etc.
Fix steps
- For related changes, batch them into one message: "refactor PlayerHandler and update its callers" beats two separate messages.
- For unrelated changes, separate messages are fine — and easier to roll back individually.
Related
- AI not responding — for stuck responses (different problem from slow responses)
- Credits and billing — priority queue details