가상 스레드 적용 전, 외부 결제 API 호출 시 응답시간 저하 변화

이전 테스트 결과

https://montmer27.tistory.com/268

HikariCP connection pool 증가 후 성능 개선 (결제 생성)

변경사항: 외부 결제 API 호출 시 300-700ms 사이 난수값으로 응답 지연이 발생하도록 설정

scenario-b

TEST-2

• test type: pressure
• 목적: 실패 지점 관찰
• test detail

pressure: [
   { target: 30, duration: '1m' },
   { target: 50, duration: '1m' },
   { target: 70, duration: '1m' },
   { target: 100, duration: '1m' },
   { target: 0, duration: '30s' },
]

test result(console)

         /\      Grafana   /‾‾/                                                                                                                                               
    /\  /  \     |\  __   /  /                                                                                                                                                
   /  \/    \    | |/ /  /   ‾‾\                                                                                                                                              
  /          \   |   (  |  (‾)  |                                                                                                                                             
 / __________ \  |_|\_\  \_____/ 


     execution: local
        script: /k6/scenario-b.js
        output: InfluxDBv1 (http://k6-influxdb:8086)

     scenarios: (100.00%) 1 scenario, 500 max VUs, 5m0s max duration (incl. graceful stop):
              * purchase_flow: Up to 100.00 iterations/s for 4m30s over 5 stages (maxVUs: 50-500, gracefulStop: 30s)

WARN[0179] Insufficient VUs, reached 500 active VUs and cannot initialize more  executor=ramping-arrival-rate scenario=purchase_flow


  █ THRESHOLDS 

    http_req_duration{phase:scenario,name:cart_add}
    ✗ 'p(95)<800' p(95)=5.8s

    http_req_duration{phase:scenario,name:order_create}
    ✗ 'p(95)<1000' p(95)=5.74s

    http_req_duration{phase:scenario,name:payment_create}
    ✗ 'p(95)<1500' p(95)=6.32s

    http_req_failed
    ✓ 'rate<0.01' rate=0.00%

      {phase:scenario}
      ✓ 'rate<0.01' rate=0.00%


  █ TOTAL RESULTS 

    checks_total.......: 24299   75.105231/s
    checks_succeeded...: 100.00% 24299 out of 24299
    checks_failed......: 0.00%   0 out of 24299

    ✓ product fetch success
    ✓ login success
    ✓ address fetch success
    ✓ cart item added 201
    ✓ order created 201
    ✓ payment processed 201

    HTTP
    http_req_duration..........................: avg=3.38s  min=3.52ms   med=4.42s  max=9.12s p(90)=5.85s p(95)=6.07s 
      { expected_response:true }...............: avg=3.38s  min=3.52ms   med=4.42s  max=9.12s p(90)=5.85s p(95)=6.07s 
      { phase:scenario,name:cart_add }.........: avg=3.32s  min=19.35ms  med=4.37s  max=9.12s p(90)=5.67s p(95)=5.8s  
      { phase:scenario,name:order_create }.....: avg=3.32s  min=3.52ms   med=4.4s   max=7.79s p(90)=5.61s p(95)=5.74s 
      { phase:scenario,name:payment_create }...: avg=3.91s  min=316.74ms med=4.94s  max=7.94s p(90)=6.18s p(95)=6.32s 
    http_req_failed............................: 0.00%  0 out of 24299
      { phase:scenario }.......................: 0.00%  0 out of 23298
    http_reqs..................................: 24299  75.105231/s

    EXECUTION
    dropped_iterations.........................: 5763   17.812727/s
    iteration_duration.........................: avg=10.57s min=343.7ms  med=15.56s max=18.4s p(90)=16.2s p(95)=16.28s
    iterations.................................: 7766   24.003754/s
    vus........................................: 13     min=0          max=500
    vus_max....................................: 500    min=50         max=500

    NETWORK
    data_received..............................: 16 MB  48 kB/s
    data_sent..................................: 8.5 MB 26 kB/s




running (5m23.5s), 000/500 VUs, 7766 complete and 0 interrupted iterations
purchase_flow ✓ [======================================] 000/500 VUs  4m30s  001.29 iters/s
ERRO[0323] thresholds on metrics 'http_req_duration{phase:scenario,name:cart_add}, http_req_duration{phase:scenario,name:order_create}, http_req_duration{phase:scenario,name:payment_create}' have been crossed

test result(graph)

지표	1차 측정	이중 락 해제 후	스케줄러 인터벌 완화 후	HikariCP 증가 후	응답 지연 적용 후	직전 대비 변화
전체 p95	5.03s	4.07s	2.94s	2.6s	6.07s	133.5% 악화
cart_add p95	5.06s	4.09s	2.95s	2.65s	5.8s	118.9% 악화
order_create p95	4.99s	4.05s	2.92s	2.54s	6.74s	165.4% 악화
payment_create p95	5.03s	4.1s	2.94s	2.61s	6.32s	142.1% 악화
평균 응답시간	2.89s	1.35s	781.73ms	630.04ms	3.38s	436.5% 악화
med 응답시간	4.31s	181.92ms	60.14ms	35.26ms	4.42s	12435.6% 악화
HTTP RPS	74.71/s	104.62/s	120.46/s	122.86/s	75.1/s	38.9% 악화
iterations	8,399	10,624	12,150	12,486	7,766	37.8% 악화
dropped iterations	5,130	2,905	1,379	1,044	5,763	451.8% 악화
iteration p95	14.43s	13s	8.75s	7.77s	16.28s	109.5% 악화