As part of https://github.com/ethyca/fidesops/pull/944 we made some changes to the execution layer pertaining to the number of open DB connections each worker could use at any one time. As part of this we fixed the --concurrency option at 2. Let's make this configurable so it can be overridden depending on a user's infra.
This could be configurable in the future, but this matches our state before the move to Celery. The default is the number of cores on your machine, but limiting the number of PrivacyRequests that can be run simultaneously per worker has a lot of positive effects. This includes reducing the number of simultaneous connections on the application database, as well as the customers' owned databases, and reduces simultaneous requests against their connected API's.
As part of https://github.com/ethyca/fidesops/pull/944 we made some changes to the execution layer pertaining to the number of open DB connections each worker could use at any one time. As part of this we fixed the
--concurrency
option at2
. Let's make this configurable so it can be overridden depending on a user's infra._Originally posted by @pattisdr in https://github.com/ethyca/fidesops/pull/944#discussion_r930980203_