응답 지연 적용 상황, HikariCP 20->30 증가 후 성능 비교

이전 테스트

https://montmer27.tistory.com/269

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

가상 스레드는 적용하지 않았음

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[0227] 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)=3.62s

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

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

    http_req_failed
    ✓ 'rate<0.01' rate=0.00%

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


  █ TOTAL RESULTS 

    checks_total.......: 32411   102.832953/s
    checks_succeeded...: 100.00% 32411 out of 32411
    checks_failed......: 0.00%   0 out of 32411

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

    HTTP
    http_req_duration..........................: avg=1.73s min=3.68ms   med=1.27s max=5.66s  p(90)=3.75s  p(95)=3.95s 
      { expected_response:true }...............: avg=1.73s min=3.68ms   med=1.27s max=5.66s  p(90)=3.75s  p(95)=3.95s 
      { phase:scenario,name:cart_add }.........: avg=1.61s min=18.05ms  med=1.23s max=5.08s  p(90)=3.51s  p(95)=3.62s 
      { phase:scenario,name:order_create }.....: avg=1.61s min=3.68ms   med=1.25s max=4.89s  p(90)=3.47s  p(95)=3.58s 
      { phase:scenario,name:payment_create }...: avg=2.14s min=312.78ms med=1.77s max=5.66s  p(90)=4.03s  p(95)=4.14s 
    http_req_failed............................: 0.00% 0 out of 32411
      { phase:scenario }.......................: 0.00% 0 out of 31410
    http_reqs..................................: 32411 102.832953/s

    EXECUTION
    dropped_iterations.........................: 3059  9.705532/s
    iteration_duration.........................: avg=5.37s min=336.98ms med=4.29s max=12.56s p(90)=10.94s p(95)=11.07s
    iterations.................................: 10470 33.219/s
    vus........................................: 5     min=0          max=500
    vus_max....................................: 500   min=50         max=500

    NETWORK
    data_received..............................: 21 MB 66 kB/s
    data_sent..................................: 11 MB 36 kB/s




running (5m15.2s), 000/500 VUs, 10470 complete and 0 interrupted iterations
purchase_flow ✓ [======================================] 000/500 VUs  4m30s  001.29 iters/s
ERRO[0315] 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

지표	HikariCP = 20	HikariCP = 30	직전 대비 변화
전체 p95	6.07s	3.95s	34.9% 완화
cart_add p95	5.8s	3.62s	37.6% 완화
order_create p95	6.74s	3.58s	46.9% 완화
payment_create p95	6.32s	4.14s	34.5% 완화
평균 응답시간	3.38s	1.73s	48.8% 완화
med 응답시간	4.42s	1.27s	71.3% 완화
HTTP RPS	75.1/s	102.83/s	36.9% 개선
iterations	7,766	10470	34.8% 개선
dropped iterations	5,763	3,059	46.9% 완화
iteration p95	16.28s	11.07	32.0% 완화

다음 목표: 더 이상 성능을 개선하지 않는 HikariCP connection pool의 최소값 찾기