-
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: refine container executor model
Motivation: In https://rb.dcache.org/r/14115 master@8a5c358af45586383d87873952407c646f81f4c6 the container executor model was made more like SRM by using an unbounded cached executor. While this brought Bulk performance in line with SRM, it also drives memory usage to be very near to physical memory. In JFR, after a sustained usage/submission of about 1700 requests of 10K targets each over 6 hours, one can observe this warning (see attached). However, a totally unbounded executor is not necessary. All that is required is an executor which has enough slots to accommodate the in-flight semaphore. Modification: Split the pooled executor into a main and a callback executor, each initialized with max threads equal to the in-flight semaphore value. Use the callback executor exclusively for message/activity callbacks (instead of direct executor). Result: Same performance as before, but with a total memory footprint at a little more than half available physical memory instead of being very close to it. Target: master Request: 9.2 Requires-notes: yes Patch: https://rb.dcache.org/r/14118/ Acked-by: Tigran Acked-by: Lea
- Loading branch information
Showing
3 changed files
with
38 additions
and
8 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