Thanks for the info Phil

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Phil Wilcock
Sent: Donnerstag, 4. Juni 2015 09:16
To: [email protected]
Subject: RE: [mssms] BITS

 

Weeeell, people are setting it to all sorts. Some are using time based
constraints – so really throttle back to 100/200kb during business hours and
let it go unlimited outside that. Others use a standard value and let BITS
get on with it, others use GPO and set different policy by location.

 

We find that even a limit of 2/3/4/5mb/s works well with BranchCache – it
just seems to behave more gracefully. If everything is going full speed then
timings can be out, and some clients can end up going back to the DP instead
of doing P2P.

 

Obviously it’s easier if you have uniform bandwidth availability across all
your sites – but who the heck has that!?

 

As for priority – CM uses Normal Priority for its Background transfers, and
Foreground (crazy unlimited) for user initiated downloads. So policy wise,
you only really need to set a rate for Normal as far as CM is concerned.

 

There is a lot you can do to avoid congestion – targeting ‘seed’ PCs at each
site for instance is popular. These nominated PCs act as a ‘beachhead’ and
if you can get content to them and into the BranchCache cache overnight then
all’s good. Apps work better than packages too as they have that
randomization built into the start time so generally one PC will kick off
ahead of the others which is ideal.

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: 03 June 2015 23:49
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

What are people setting it to. “That depends on your network”. Doh…

 

Still, any pointers, especially with those priority settings.

Is unlimited a good thing at all?

 

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Phil Wilcock
Sent: Dienstag, 2. Juni 2015 21:27
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

In general, BITS will attempt to scale back a transfer’s bandwidth usage for
as long as there’s bandwidth contention it can detect , which means “over
the same IGD (Internet Gateway Device)” if the IGD supports the right kind
of traffic counter queries, or “from the same machine” otherwise), and it
will retry-after-xx seconds for many types of outright failures to transfer.

 

In reality – BITS doesn’t get the info from the IGD, so it reverts to using
the NIC speed as it’s available bandwidth which is less than ideal, so it’s
best to throttle it using policy. In our testing we found that BranchCache
worked even better if BITS was throttled – even just slightly.

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: 02 June 2015 19:57
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

What is BITS really doing to no get into the way or throttle?

 

What I thought, it basically only knows what else is on the NIC is uses, it
doesn’t know if there is anything else in the pipe.

True?

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Marcum, John
Sent: Dienstag, 2. Juni 2015 20:08
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

Someone once told me the only way to know how fast you can go on a given
road was to try it too fast once. 

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Andreas Hammarskjöld
Sent: Tuesday, June 2, 2015 2:43 AM
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

We talked about this senior… *sigh* so many times. This is a wet dream that
will never come through. 

 

Gonna open up a can of worms with this but here it goes. The ONLY way (and
the “other vendors” will tell you different with their mumbo-jumbo
technology) you can tell how much bandwidth you got on a pipe is to try to
cram as much data through as possible for a period of time. WAN software
today is very sophisticated and will allow bursts etc. for periods of time
depending on certain scenarios.

 

Far more superior people have done many hours on this subject: The A**shole
project, sorry Assolo, got some very interesting reading:
http://netlab-mn.unipv.it/assolo/ 

 

Think of it like answering this question, how fast can you go on a certain
road?

 

//A

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Phil Wilcock
Sent: den 2 juni 2015 09:29
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

Haha – wasn’t expecting that Roland :)

 

My number 1 is – Accurate end-to-end bandwidth calculation..

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Andreas Hammarskjöld
Sent: 02 June 2015 08:18
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

Oh man!!! :)

 

//A

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: den 2 juni 2015 08:29
To: [email protected] <mailto:[email protected]> 
Subject: RE: [mssms] BITS

 

Make it work better? Make it work like OneSite? :)

 

 

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Andreas Hammarskjöld
Sent: Montag, 1. Juni 2015 22:25
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] BITS

 

Hey,

 

Got an upcoming meeting with the BITS dev team, anything that you guys see
missing that should be fixed? Or something that you never found the answer
too?

 

Anything accepted as long as it’s not in the form of “make it work”. :)

 

Br,

 

//Andreas

 

----------------------------------

Co-Founder

+46727253995

http://2PintSoftware.com

http://twitter.com/AndHammarskjold 

 

 

 

 

 

 

  _____  


Confidentiality Notice: This e-mail is from a law firm and may be protected
by the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and
then delete it from your computer.

 

 

 

 

 




Reply via email to