Difference: XrootdThrottling (2 vs. 3)

Revision 32013-01-07 - BrianBockelman

Line: 1 to 1
META TOPICPARENT name="CmsXrootdArchitecture"

Throttling Xrootd

Line: 35 to 35
  • Network-level: Most modern managed switches can do flow shaping. This is the preferred solution, as the bottleneck is more often in the network than at the host level.
We recommend to distinguish the xrootd and gridftp traffic at your site and apply the appropriate policy.
Note: We are developing experimental support for bandwidth throttling in Xrootd; see this page for more information.

I/O Operations Per Second (IOPS)

In CMSSW-based workflows, IOPS is a greater concern than raw bandwidth. Many uses can cause a huge number of small reads, especially in older versions. Always recommend users adopt a 4_x release, preferably 4_2 or later.

Line: 45 to 47
  We suggest a reactive approach. You can monitor how much activity goes on through your site from our detailed monitoring collector.
Note: We are developing experimental support for IOPS and concurrency throttling in Xrootd; see this page for more information.
META FILEATTACHMENT attachment="XrootdSharedStorage.png" attr="" comment="" date="1299705260" name="XrootdSharedStorage.png" path="XrootdSharedStorage.png" size="33936" stream="XrootdSharedStorage.png" tmpFilename="/usr/tmp/CGItemp32789" user="bbockelm" version="1"
META FILEATTACHMENT attachment="XrootdSharedStorage2.png" attr="" comment="" date="1299705275" name="XrootdSharedStorage2.png" path="XrootdSharedStorage2.png" size="32264" stream="XrootdSharedStorage2.png" tmpFilename="/usr/tmp/CGItemp32812" user="bbockelm" version="1"
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback