Performance Tips
Supervertaler is designed to stay responsive on large projects, but performance can vary with project size and enabled features.
Tips
- Pick a smaller Per page size for very large projects (the grid shows all segments by default; projects over 1,000 segments auto-paginate at 200). See Pagination
- Keep only the needed TMs and termbases enabled
- If semantic search is enabled, allow indexing to complete
Quick wins when it feels slow
- Disable spellcheck temporarily (Settings → View Settings)
- Close other heavy apps (browsers with many tabs, IDE builds, etc.)
- Restart Supervertaler and reopen the project
Large projects
Very large files (thousands of segments) can stress any UI grid.
- Prefer pagination.
- Consider splitting source documents or using multi-file projects.
A slow start-up with a TM message in the log
If the log says “[TM] The full-text index cannot find its own rows… Rebuilding it”, Supervertaler is repairing the search index that fuzzy TM matches rely on (from v1.10.371). On a large TM this takes a few seconds, about 2.6 seconds for 200,000 entries, and it happens only when the index needs it. See TM Matches Not Appearing.
If it feels slow
Try restarting the app and reopening the project.
If performance is still poor, note:
- Project size (segment count)
- Whether spellcheck is enabled
- Which CAT format you imported