Hey guys, I’m not sure if something changed from when I last used this a year or so ago, but using the setting below doesn’t appear to throttle at all.
setting "_BESGather_Download_LimitBytesPerSecond "=“46875” on “{now}” for client
When I used a calculator, this was close to 1/4 of a T1 circuit, which is what I am wanting to test with. I even tried half of that, no change at all. I verified the property is on the endpoint that I am testing on, which is a Relay and I am attempting to throttle the rate at which it is downloading from it’s parent relay. Also, I have version 9.2.2.21, any help would be greatly appreciated, thank you.
Yep, I remember that I believe. You mean that if a download is already being pushed prior to the new setting in place, it will not be affected, right? However, this setting is not changing anything, even if I push a file after it has been applied.
The setting makes the “client” (in the client/server terminology) tell its “server” that it wants to restrict bandwidth, so to make sure you are testing the communication with the computer that the setting is placed on and the parent above it correct?
Correct, I placed the setting on my client/relay itself, hoping to restrict the rate at which it is downloading from its parent relay/server. I did not place any settings on the parent relay itself.
My main version is 9.2.2.21, but my relays are at version 9.2.1.48, along with my clients.
So the setting you made would affect the Relay only (not the client).
Additionally one of the issues with client side bandwidth throttling…
Client-side throttling (Client/Relay) is expressed as an amount of bandwidth to be used on a single upstream connection. Note that Clients may use more bandwidth if they have multiple simultaneous upstream connections.
So on the “Server” or the parent of this relay, do you have the _BESRelay_HTTPServer_ThrottleKBPS setting on there which will limit the maximum bandwidth for that relay to use (if that is appropriate)?
I do not have the throttle setting on the server/parent relay because I don’t want to throttle the other 300 clients that are also being fed by this relay.
So what you are saying is that I need to change the client setting for throttling, not the relay setting, even though my client does have a relay installed? Understood on the multiple streams. I am pushing a few GBs of data and don’t have the time to do so at night, and have to push it during the day so I want to limit impact.
No, the local client will talk over loopback to the local relay. The relay will potentially make multiple requests to its parent relay and each request will be limited by the _BESGather_Download_LimitBytesPerSecond setting. So unless the “parent” or “server” has the other setting it won’t combine all those requests into one from the standpoint of the bandwidth. We don’t have a “for this IP only use this amount of bandwidth” type of setting at this point.
Hey Alan, I think I understand what you are saying, but the setting I used on the relay isn’t throttling anything at all when downloading from the parent relay/server. Even though I didn’t put the other throttle setting on the outbound of the parent/server, I should still be seeing some throttling, agreed? Did I choose the correct setting? If so, why isn’t it working at all in this scenario. Thank you for your time.
There was an Frigginng space at the end of my setting before the last quotation mark. Sorry Alan, it is working as advertised now. I will crawl back into my cave
There is one other issue associated with this that I don’t think it is bandwidth throttling related, but I figured that I would ask because it seems very odd. I noticed that on the relay that I am pushing the 1GB file down to that the client is on the same machine is trying to actively download this 1GB file from previous actions that are now stopped and removed. I will restart the BES services on the endpoint, and it doesn’t matter, within a few minutes I will see multiple active downloads from previously stopped actions. Is there some place on the main server or relay that it starting this prefetch until it actually completes? Thank you
Ahh those are hard to tell but I wonder if the client log would have shown the setting failure? Or was it typed in manually? Yeah they revert to the default if it doesn’t understand the value
Sorry to revive this, but is there a way from the client/relay to limit the number of simultaneous upstream connections? I’m in a similar situation, where I need a particular Relay “2” to limit its download speed from its upstream Relay"1", without affecting the other clients of Relay “1”.
