Performance Internals (Advanced)
This page explains how performance optimizations work at a system level.
Virtual scroll
For large documents, the editor uses virtual scrolling:
- Only visible lines are rendered
- Scrolling loads new content dynamically
- This prevents the browser from slowing down with thousands of DOM elements
Virtual scroll activates automatically when a document exceeds a size threshold.
Background workers
Heavy operations run in separate threads:
- Diff computation — comparing two documents
- Tree search — finding matches across all keys and values
- Formatting — pretty-print and minify for large files
These operations do not block typing or interaction.
Read-only fallback
When a document is extremely large:
- The editor switches to a read-only optimized view
- This prevents performance degradation
- You can still browse and search the content
Tree pagination
For arrays with many children:
- Items are loaded in pages
- “Show more” controls let you expand as needed
- This prevents rendering thousands of nodes at once
Design principles
- Responsiveness is always prioritized
- Heavy work happens in the background
- The editor adapts automatically — no configuration needed
Back to: Performance
Last updated on