Throughput
Throughput describes work processed per period. It is neither the duration of one request nor the number of concurrent users.
Throughput describes how much work a system processes within a period. Completed requests per minute can be one unit. Which operations and outcomes are counted must be defined.
A hypothetical example
A portal successfully completes 120 requests per minute. That averages 2 per second. It does not mean each request takes 500 ms: requests can overlap and run for different durations.
Throughput and response time answer different questions. The number of concurrent users is another separate value. Comparisons need compatible work types, load and success criteria. Failed or incomplete operations must not silently count as equivalent completions.
Sources
Related terms
- Response timeResponse time needs a defined start and end. Fetching an API response and reaching a usable view measure different sections.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
- Cache invalidationCache invalidation ends reuse of a stored copy under defined rules. The source record remains a separate concern.
- CachingCaching reuses stored data or results. Validity and the permitted user scope belong in the design.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps