Performance and scaling

The software sends batches of Read-ProjectResource requests to the SemaphoreUI server. This creates a queue and blocks any other requests during this time, because SemaphoreUI only runs tasks consecutively (in particular if they use the same template or, more precisely, the same git repository). This can lead to failures in the software (e.g. observed with the creation of an S3 access key pair) due to the unexpected delay.

This Problem happens now in the test phase, without a significant amount of users.