---
title: "Concurrency"
description: "2 posts about Concurrency, summarised, each linking to the original."
---

# Concurrency
> 2 posts about Concurrency, summarised, each linking to the original.

## Articles

### [How we raised Databricks cluster rate limits by 7.5×](https://yomu.fyi/post/how-we-raised-databricks-cluster-rate-limits-by-7-5x.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Heqing Ya, Tan Zhang, Ankit Batra, Abhishek Rai
- Published: Nov 18, 2026
- Type: Problem & solution

Databricks’ Compute Platform team replaced fixed request-rate limits for cluster creation with adaptive concurrency limits to better handle long-running, variable-cost operations. Fixed limits turned away requests during healthy periods yet accepted too many when dependencies slowed, requiring manual tuning. Adaptive concurrency tracks active provisioning workflows with slots and adjusts the slot count based on congestion signals such as provisioning latency and thread pool saturation. The rollout analysis reported a 7.5× increase in default cluster-creation request-rate limits, more than 99.99% fewer rate-limit errors, and removal of over a hundred customer-specific overrides. The fixed API request-rate limit remains as a final safety guardrail against exceptionally high incoming traffic.


### [Your .NET parallel loop can become serial in a one-CPU container](https://yomu.fyi/post/your-net-parallel-loop-can-become-serial-in-a-one-cpu-container.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Guilherme Appel
- Published: Nov 4, 2026
- Type: Problem & solution

In a .NET container with a one-CPU limit, Parallel.ForEachAsync defaults its MaxDegreeOfParallelism to Environment.ProcessorCount, which returns 1, causing I/O-bound calls to run serially. The author’s lab processed 200 records, each requiring three enrichment calls and one write, taking 83.6 seconds with one CPU versus 42.1 seconds with two. The solution uses a DependencyBudgets class with separate SemaphoreSlim instances per dependency to cap concurrency independently. Strategy C4, with 24 enrichment permits and 6 write permits, avoided all HTTP 503 rejections while accepting 35.08 records per second in a slow write scenario. The author recommends configuring per-dependency concurrency limits, validating them at startup, and using separate timeouts for service calls and permit waits.
