LeetCode Judge System: Asynchronous Result Delivery Latency

Execution Queue Behavior

LeetCode utilizes a distributed judge system to execute code submissions in isolated sandboxes. When a user triggers the 'Run Code' or 'Submit' action, the request is queued and processed asynchronously, with the final result delivered via polling or websocket mechanisms.

Resource Constraints

The environment enforces strict time and memory limits to prevent resource exhaustion on judge nodes. While standard streams (stdin/stdout) are captured for the user interface, the internal prioritization of the execution queue and the mechanism for handling high-concurrency bursts are not fully transparent.

Given the asynchronous nature of the judge, there is uncertainty regarding how the system maintains result ordering and manages latency during periods of peak load.

• Does the judge system guarantee the sequential processing of test cases for a single submission?
• What mechanism determines the priority of 'Run Code' requests versus 'Submit' requests in the distributed queue?