Preload vs Lazy‑Load PyScript Runtime: Trade‑off for Concurrent Request Latency

Latency Impact of Runtime Loading Strategies

Using a shared <py-config> with preloading significantly reduces the per-tag latency for concurrent <py-script> executions. Because PyScript initializes a single interpreter singleton per page, preloading ensures the WebAssembly (WASM) binaries are fetched and the environment is ready before the scripts are triggered. In contrast, lazy-loading multiple concurrent tags can create a "waterfall" effect where the browser attempts to resolve the runtime dependency for each tag, leading to increased time-to-first-output for the subsequent scripts.

Trade-offs: Initial Load vs. Execution Speed

The primary trade-off is between Time to Interactive (TTI) and Execution Latency:

• Preloading: Increases initial page load time and may delay the first paint if the runtime is fetched synchronously. However, it eliminates the fetch-and-init delay when the Python scripts actually run.
• Lazy-Loading: Optimizes the initial page load and reduces bandwidth for users who may never trigger the Python functionality. The cost is a measurable "freeze" or delay during the first execution as the runtime initializes.

Analysis of Concurrent Execution and the GIL

Regarding the Global Interpreter Lock (GIL), it is important to distinguish between network latency and execution contention. While the runtime is shared, PyScript (via Pyodide) currently operates in a single-threaded environment within the browser's main thread. Therefore, concurrent <py-script> tags do not execute in true parallel; they are queued. Any observed latency during concurrent execution is more likely attributed to the sequential nature of the JavaScript event loop and the initial runtime setup rather than GIL contention in the traditional multi-threaded sense.

Verification Steps

To quantify these effects in your specific environment, use the following approach:

1. Network Baseline: Open Browser DevTools (Network Tab) with "Disable Cache" checked. Compare the DOMContentLoaded event time between a preloaded config and a lazy-loaded setup.
2. Execution Timing: Use the performance.now() API to measure the delta between the insertion of the <py-script> tag and the first print() output.
3. Concurrency Test: Insert five <py-script> tags simultaneously and record the time to completion for the final tag in both loading scenarios.

Missing Diagnostic: To refine this recommendation, please specify if your scripts are performing heavy CPU-bound computations or primarily lightweight DOM manipulations, as this determines if the main-thread blocking of preloading outweighs the execution benefits.