Search View vs. Search Editor for large dataset navigation

When performing a regex search across a large monorepo in Visual Studio Code, there is a distinct trade-off between using the standard Search View and the Search Editor. The Search View utilizes a virtualized list to stream results incrementally, which minimizes initial memory overhead during navigation.

Conversely, the Search Editor generates a persistent document of all matches. While this allows for saving the results as a file for curation or refactoring, it introduces potential memory pressure as the result set grows.

For a dataset containing tens of thousands of matches, it is unclear at what threshold the Search Editor's document-based approach becomes a performance bottleneck compared to the Search View's paginated streaming.

• Which interface is more efficient for navigating result sets that exceed available system memory?
• Does the Search Editor implement any internal pagination or virtualization to mitigate memory consumption for extremely large files?