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 problems when huge number of portal aliases is in use #2513

Closed
4 of 6 tasks
mikebigun opened this issue Dec 13, 2018 · 0 comments · Fixed by #2514
Closed
4 of 6 tasks

Performance problems when huge number of portal aliases is in use #2513

mikebigun opened this issue Dec 13, 2018 · 0 comments · Fixed by #2514
Labels
esw Issues reported by ESW team or Evoq customers

Comments

@mikebigun
Copy link
Contributor

Description of bug

Customer complains about huge performance degradation when around ~5K portals/aliases is in use with a combination of ~2K requests executed at the same time. Whole system becomes very slow and sometimes is coming up to an unresponsive state.
Tracing the system customer identified the problem on a web server. Using various tools identified that many threads are locked out due to very low capability to validate portal aliases during the incoming requests.

Steps to reproduce

Issue is reproducible having following database characteristics:
440k users
500k files
4885 portal alias
2000+ portals
Also, need to simulate 2K+ requests to see the problem.

Current result

System is extremely slow.

Expected result

Need to improve performance.

Affected version

  • 9.2.2
  • 9.2.1
  • 9.2
  • 9.1.1
  • 9.1
  • 9.0
@daguiler daguiler added the esw Issues reported by ESW team or Evoq customers label Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
esw Issues reported by ESW team or Evoq customers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants