-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dcache-bulk: use rate limiter to throttle semaphore release
Motivation: master@0b4140b454b819de55c7c412539294537ff0beb8 https://rb.dcache.org/r/14118/ restructured the container job for greater throughput. In order to pace execution of calls on external services, however, two semaphores were used. For task execution, the semaphore is not released until the future of the execution completes. This works well but has the drawback of not allowing submission to continue to services like PinManager if there are max permit number of tasks waiting for a response (e.g., in the case of actual staging). On the other hand, releasing the semaphore immediately upon reception of the future, causes calls to external services to pile up, causing timeout errors of various sorts. Modification: Relying on the thread pool size will not work in this case because the execution of the activity must be asynchronous; the turnover is extremely rapid. Instead we adopt the solution of a rate limiter to throttle the semaphore release. Each activity is given a limiter for the service endpoint it communicates with. The rates for these (PinManager, PnfsManager, QoSEngine) are configurable. Result: Performance and stability is sustained, but throughput continues when the submitted task activities are in a state of waiting for future completion. Target: master Request: 9.2 (fixes an important issue) Patch: https://rb.dcache.org/r/14136/ Requires-notes: yes (No longer blocks throughput of new tasks when the number of tasks waiting for completion from an external service like PinManager reaches max available task permits.) Acked-by: Tigran
- Loading branch information
Showing
7 changed files
with
180 additions
and
65 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.