|
|
|
The thing is that we only have few builds which should run in amazon. The resource is pretty specific. So on every request processing run all currently queued requests are checked against the cloud profile and that takes a long time even when no resource (just for 1-2 configurations) will ever match on the cloud profiles.
I checked the code and the only possible reason for the long loop is because that new EC2 nodes are launched in the loop. And this happens only when no existing nodes/available resources matches the build requirement, and some cloud profiles matches. Can you please check if this is the case at your side?
|
Build request processing itself is multi-threading, but at least we need to have a single thread main loop to go through the build requests and allocate resources one by one.