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

Unify configuring AET testing throughput #361

Open
malaskowski opened this issue Sep 19, 2018 · 0 comments
Open

Unify configuring AET testing throughput #361

malaskowski opened this issue Sep 19, 2018 · 0 comments
Labels
enhancement size medium Issues that would require some thinking and tinkering to fix

Comments

@malaskowski
Copy link
Contributor

Version used

  • AET 3.0.0

Context of the feature

Now to properly configure AET testing throughput (number of concurrent tested urls) several different configurations that values are correlated needs to be adjusted:

  1. RunnerConfiguration.maxMessagesInCollectorQueue which tells how many collection tasks can be scheduled in the system in one time
  2. CollectorMessageListenerImpl configurations, each config entry (this is OSGi config factory) spawns new Collector worker, number of those workers also limits the maximum number of concurrent collect tasks done in the system.
  3. Number of browsers in the system (number of Selenium Grid Nodes browsers).

At least configs 1 and 2 should be configurable more intuitively, e.g. there should be one configuration, where user sets the number of browsers that are in the system, or even better, if this is possible, number of browsers should be detected automatically and 1, 2 set automatically.

@tMaxx tMaxx added size small Quick fixes and minimal-effort issues size medium Issues that would require some thinking and tinkering to fix and removed size small Quick fixes and minimal-effort issues labels Sep 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement size medium Issues that would require some thinking and tinkering to fix
Projects
None yet
Development

No branches or pull requests

2 participants