Performance issues when choosing a tag with a large number of tenants on the create deployment screen.

[Flamage82]

When selecting a tag on the create deployment screen, the tag is resolved to a list of tenants, and then we query the server 4 times for each tenant. This amounts to 1600 requests for a tag with 200 tenants, when you include OPTIONS requests.

I propose to allow a tag to be passed directly to the API in these circumstances, which would reduce the number of calls to 4 for a single tag.

[adamwhitekallidus]

Any idea when this bug will be fixed? We are adding new tenants all the time and each one is making the performance worse and worse!

[Flamage82]

@adamwhitekallidus Sorry about the delay. Things have been a little hectic, and I've been unable to complete a fix for this issue yet. @johnsimons has kindly offered to take over this task and hopefully we will have something for you soon.

[johnsimons]

Release Note: Improvements for when choosing a tag with a large number of tenants on the create deployment screen

[michaelnoonan]

This change caused a DOA for 2018.5.0. We have reopened the issue to be addressed in a later patch. The regression was fixed by #4556

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.