Code Review: Batched Processor Fallback and Capacity Bug
A PR replacing a synchronous processor with a batched processor fails to fall back to the synchronous processor if the batched processor cannot be created, returning None instead. Additionally, the batched processor's documented throughput of 6k requests/second falls short of the peak load of 8k requests/second noted in the README.
Asked at:
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late July, 2026
Senior
I was given a PR for an issue where some python app was crashing under heavy load. The PR changed the existing synchronous processor (one request at a time) to a batched processor (40 requests at a time). The repo still had the synchronous processor for reference. However, if the batched processor failed to create, the new code returned None, instead of falling back to the synchronous processor. I pointed this out. Also - the PR description mentioned that the new batched processor could handle 6k/s/instance, while the peak load (as per the README.md) was 8k/s/instance. I didn’t use AI at all for any help, as I was very confused by the format (being my 1st such interview), and this was an AI-assisted interview.
Your account is free and you can post anonymously if you choose.