Which context mode is optimal for paginating large datasets via Node.js fs modules?

When building a desktop application with NW.js, developers often need to process large datasets stored in local files and display them in a paginated UI. This requires a bridge between the Node.js fs module for data retrieval and the Chromium DOM for rendering.

The framework offers two primary execution environments: mixed context and separate context. The choice between these affects how the global object is shared and how data is passed between the Node.js runtime and the browser engine.

For a scenario involving frequent, high-volume data reads and updates to the DOM, it is unclear which mode minimizes overhead and prevents memory leaks during pagination.

• Does mixed context provide a performance advantage for large data transfers by eliminating the boundary between Node and the DOM?
• What are the implications for garbage collection when passing large buffers from Node.js to the window object in separate context mode?