You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Prepare AET environment with large database (e.g. at least 100 GB in size / few hundreds of suites, each with few hundred versions)
Go to /config/list
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.
The text was updated successfully, but these errors were encountered:
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.
AET 3.2.2
To Reproduce
Steps to reproduce the behavior:
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.
The text was updated successfully, but these errors were encountered: