Understanding High Concurrency: Definition, Key Metrics, and Relationship with Multithreading
High concurrency refers to a short period where a system receives a massive number of requests, such as ticket‑booking spikes, and is measured by metrics like response time, throughput, QPS, and concurrent users, while multithreading is merely one programming technique to handle such load, not synonymous with high concurrency.
What is High Concurrency
High Concurrency (High Concurrency) describes a situation where a system encounters a large number of operation requests within a short time, commonly seen in web systems with massive traffic such as ticket‑booking spikes (e.g., 12306) or large e‑commerce events (e.g., Tmall Double‑11).
This surge leads the system to execute many operations simultaneously, including resource requests and database accesses.
Key Metrics for High Concurrency
1. Response Time – The time the system takes to respond to a request, e.g., processing an HTTP request in 200 ms means the response time is 200 ms.
2. Throughput – The number of requests processed per unit of time.
3. Queries Per Second (QPS) – The number of requests responded to each second; in many internet contexts this metric overlaps with throughput.
4. Concurrent Users – The number of users simultaneously using the system’s functions, such as the online user count in an instant‑messaging service.
Relationship Between High Concurrency and Multithreading
High concurrency and multithreading are often mentioned together, but they are not equivalent; high concurrency ≠ multithreading .
Multithreading is a programming technique that can be used to handle high concurrency, but high concurrency is a language‑agnostic concept aimed at delivering better internet services. Achieving high concurrency requires system‑wide optimizations across hardware, network, architecture, language choice, data structures, algorithms, database tuning, etc., with multithreading being just one possible solution.
Mike Chen's Internet Architecture
Over ten years of BAT architecture experience, shared generously!
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.