Explore if Workhorse API limits should be pinned to Puma thread count automatically

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

While working on adding Hybrid Reference Architecture support to GET it was suggested that the apiLimit argument along with some others should be set for Workhorse to be close to total Puma thread count:

-apiLimit 11 -apiQueueLimit 200 -apiQueueDuration 60s

If this is indeed recommended then it's better to be set automatically in Omnibus (and Charts) so everyone can benefit. Since Puma thread count in Omnibus is set automatically Workhorse API limits should be the same.