Tokio Gives Progress, Not Ordering: Scheduling 1M Tasks

The author discusses how Tokio's scheduling behavior led to unexpected memory usage spikes when spawning a large number of tasks concurrently, and how adding a semaphore to bound the number of tasks helped reduce the memory usage.