개발 창고/Server

How to handle high volume traffic

로이제로 2024. 8. 12. 22:00
반응형


TOC is not supported in this version (ex.Mobile)


Criteria for evaluating high volume traffic

TPS (Transaction Per Second)

 The number of transactions processed per second. The higher the TPS, the higher the system's ability to handle large amounts of traffic.

QPS (Query Per Second)

 The number of queries handled per second. A higher QPS means a higher capacity of the system to handle large amounts of traffic.

Latency

 Average amount of time the system takes to process requests. Longer delays can degrade the user experience. For example, if you provide a service that tracks a user's location in real time, the throughput should be high per second. Additionally, if you want to display user location information on a map, the latency should be low.


Considerations for High-Capacity Traffic

Concurrent Users

 It refers to the number of users accessing a service within the same amount of time. Large amounts of traffic occur when there are many concurrent users. Services that are open at certain times, such as signing events, event winning announcements, time sales, and ticket reservations, will deal with this large amounts of traffic. Typically, more than 100,000 concurrent connections are considered large amounts of traffic.

Request Transfer

 This refers to the number of requests coming into the server, which is typically considered high-volume traffic if you need to process more than 1,000 requests per second. Performance targets should be able to process at least 1,000 requests per second.

Data Transfer

 Large amounts of traffic depend on the data that users upload and download or the size of the page the server provides. Services or media streaming platforms that download large files will have to handle large amounts of data transmission. Generally speaking, if you need to process more than 10MB of data per second, it is considered large amounts of traffic.

Response Time

 This is how long it takes the server to respond. The ideal response time for large amounts of traffic is to remain below 100 milliseconds. Optimized systems should maintain response time to requests to provide a good user experience even when under heavy load.

Server Resource Utilization

 Monitoring the server's CPU, memory disk space, and other resources is required. Sufficient server resources are required to handle large amounts of traffic.

반응형

'개발 창고 > Server' 카테고리의 다른 글

[CentOS] How to use tar  (43) 2024.04.02
[Ubuntu] 확장자 일괄 처리  (9) 2023.12.26
[AWS] How to build WordPress with LightSail  (0) 2023.12.04
[Linux] How to use /etc/fstab file  (0) 2023.11.13
[Linux] How to use "smbclient" command  (0) 2023.11.12