Concurrency · interview question

What is the healthiest performance judgment around semaphores, timeouts, and cancellation?

Multiple choiceMediumchapter-15-curatedpremiumconcurrencysemaphores-timeouts-and-cancellation

python

semaphore = asyncio.Semaphore(10)

async with semaphore:
    await asyncio.wait_for(fetch_order("ORD-1"), timeout=2.0)

Delay clarity until production traffic reveals the edge case and then patch it under pressure.Keep semaphores, timeouts, and cancellation implicit so the script stays short and hope the next engineer infers the rule.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.Solve the symptom with comments only and avoid changing the code shape around semaphores, timeouts, and cancellation.

Answer and explanation

Correct answer

C. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Why

Premature optimization is usually weaker than targeted optimization backed by measurement.

Test yourself on Concurrency

A free test with instant, explained results. No account needed.

Start free test

All Concurrency questions →

What is the healthiest performance judgment around semaphores, timeouts, and cancellation?

Correct answer

Why

More Concurrency questions