Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance tests for contact auto-complete #378

Closed
chibenwa opened this issue Mar 23, 2022 · 9 comments
Closed

Performance tests for contact auto-complete #378

chibenwa opened this issue Mar 23, 2022 · 9 comments
Assignees
Labels
I Time spent (1 halth day)

Comments

@chibenwa
Copy link
Member

  • Write a gatling scenario exercising contact search
  • Run it on preprod
  • Compare with OpenPaaS results.
@vttranlina vttranlina self-assigned this Apr 12, 2022
@vttranlina vttranlina added the II Time spent (2 halth day) label Apr 13, 2022
@vttranlina
Copy link
Member

  • Run it on preprod: wait for lsc script to generate sample data

@vttranlina
Copy link
Member

Gatling scenario linagora/james-gatling#134

@vttranlina vttranlina removed their assignment Apr 28, 2022
@quantranhong1999 quantranhong1999 self-assigned this Apr 28, 2022
@quantranhong1999 quantranhong1999 removed the II Time spent (2 halth day) label Apr 28, 2022
@quantranhong1999
Copy link
Member

quantranhong1999 commented Apr 28, 2022

At first, I run the default AC simulation with 5k users, 3 James pods => too much AC req/s leading timeout (>60s auto-complete).

I reduced the AC throughput by pausing it every 2 seconds.

1k users, ~300 mean AC req/s, peek 500 req/s (enabled glowroot)

image.png

Please open the following file: /home/hqtran/repo/james-gatling/target/gatling/tmailcontactautocompletesimulation-20220428053320298/index.html

1k5 users, mean 380 req/s, peek 600 req/s (enabled glowroot)

Started to have few requests timeout.
image

Please open the following file: /home/hqtran/repo/james-gatling/target/gatling/tmailcontactautocompletesimulation-20220428073125494/index.html

Will disable glowroot to see the impact.

@Arsnael
Copy link
Member

Arsnael commented Apr 28, 2022

Indeed... I just rechecked the simulation, no pause is too much and not really realistic either.

Wondering if shouldn't even put the pause a bit higher...

@quantranhong1999
Copy link
Member

quantranhong1999 commented Apr 28, 2022

Indeed... I just rechecked the simulation, no pause is too much and not really realistic either.

In during section, we had been sending the auto-complete request repeatedly with no pause (up to 4 millions request in 200 seconds)

@Arsnael
Copy link
Member

Arsnael commented Apr 28, 2022

Yes we should add a pause :)

@quantranhong1999
Copy link
Member

Yes we should add a pause :)

linagora/james-gatling#137

@quantranhong1999
Copy link
Member

1k2 users, mean ~350 req/s, peek ~600 req/s disabled glowroot, warmed up

image

Please open the following file: /home/hqtran/repo/james-gatling/target/gatling/tmailcontactautocompletesimulation-20220428085742516/index.html

I think we can say our Auto-complete is at 350 request/s.

@vttranlina
Copy link
Member

1k2 users, mean ~350 req/s, peek ~600 req/s disabled glowroot, warmed up

How many contacts?

@quantranhong1999 quantranhong1999 added the I Time spent (1 halth day) label Apr 29, 2022
@chibenwa chibenwa closed this as completed May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I Time spent (1 halth day)
Projects
None yet
Development

No branches or pull requests

4 participants