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 of generating /configs/list response #519

Closed
tkaik opened this issue Aug 9, 2019 · 0 comments · Fixed by #522
Closed

Performance of generating /configs/list response #519

tkaik opened this issue Aug 9, 2019 · 0 comments · Fixed by #522

Comments

@tkaik
Copy link
Contributor

tkaik commented Aug 9, 2019

Describe the bug
For large AET databases, getting response from /configs/list endpoint takes a very long time and consumes a lot of system resources (RAM, CPU) which might heavily impact performance of running suites in the system.

  • Version used: AET 3.2.2

To Reproduce
Steps to reproduce the behavior:

  1. Prepare AET environment with large database (e.g. at least 100 GB in size / few hundreds of suites, each with few hundred versions)
  2. Go to /config/list
  3. Wait for reponse

Expected behavior
Response should be returned quickly even for large databases. Response content may be limited to last X versions of report for each suite, instead of always returning every availalbe raport URL.

Additional context
Currently /configs/list endpoint is building full HTML response with StringBuilder. Consider chaning this approach. It also may be worth to check if executed DB queries are using indexes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants