Network use defaults and settings

[Ken Carlile]

Hi folks, 

I noticed that the description of the way the network use defaults set up concurrency and parallelism has changed (https://docs.globus.org/globus-connect-server/v5.4/#setting_endpoint_network_use_options)

I believe that it used to be an absolute number for Normal and Aggressive for the settings, but now it is a multiplier. Is it safe to assume that the Custom settings are also now multipliers? 

In my case, I have 8 DTNs, and I want to set a storage gateway to only use a concurrency of 1 per server with parallelism of 8 per server. This is a test for transfers between collections that are hosted on my endpoint--I've been seeing timeouts from folks doing transfers with lots and lots of small files from an internal collection to the _same_ internal collection. 

Thanks, 

Ken

[James Kube]

Hi Ken,

You're correct regarding the NetworkUse settings for the canned 'Normal' and 'Aggressive' configurations being a multiple of the number of nodes supporting an Endpoint; however, for both 'Custom' and 'Minimal,' the number of node supporting a given Endpoint are non-impactful and their respective values are read in as static values: 

• Minimal -
• Max/Preferred Concurrency - 1
• Max/Preferred Parallelism: 1
  
  
• Custom - 
• Max/Preferred Concurrency - ${value_specified_regardless_of_node_count}
• Max/Preferred Parallelism: ${value_specified_regardless_of_node_count}

Also, we're more than happy to help troubleshoot any error's being encountered, if you'd like a second set of eyes please open a ticket (via our Support Portal or via e-mail to sup...@globus.org), including a few example TaskID's encountering timeouts, and we'll further investigate.

Thank you,

James

--

James Kube
Technical Support Engineer

University of Chicago, Globus
www.globus.org