[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Conduct load testing\n\nLoad testing can determine whether your system will scale successfully during\nproduction use, and find any bottlenecks that prevent it from scaling during an\nevent.\n\n1. **Three to five months before your event**, you should perform load testing\n on critical projects and workloads to simulate peak traffic.\n\n2. Investigate the quota and cost implications of the load tests and consider\n creating [Cloud Billing budget alerts](/billing/docs/how-to/budgets) that\n will monitor the expense of the services that you are going to stress the most.\n\n3. After each test, evaluate the results and use Capacity Planner to\n visualize your usage and forecast data, and request quota increases as necessary.\n For more information, see\n [Use Capacity Planner](/support/docs/peak-events/secure-capacity#use-planner)\n and [Request a quota adjustment](/support/docs/peak-events/secure-capacity#quota).\n\nIf you require assistance, contact your account team or TAM. They can help you\ncapture and plan architecture changes to improve the overall reliability and\navailability of your services.\n\nWhat's next\n-----------\n\n- [Conduct disaster recovery testing](/support/docs/peak-events/conduct-disaster-recovery-testing)"]]
