I got excited when I saw that fancy Microsoft Message Analyzer tool and wanted to try it out. Sadly it appears to be retired and removed by MSFT? Sad!
Yeah, I have no idea either why Microsoft would want to remove Message Analyzer completely, even if they could not maintain it. You can still download it through the Internet Archive: * 32-bit x86: https://web.archive.org/web/20191104120802/https://download.... * 64-bit x86: https://web.archive.org/web/20190420141924/http://download.m... (those links via: https://www.reddit.com/r/sysadmin/comments/e4qocq/microsoft_..…
Boosting upload speed and improving Windows' TCP stack
91–100 of 127 posts
Re: Boosting upload speed and improving Windows' TCP stack
#92How come Linux doesn't have this issue? Why did Microsoft had to fix TCP with the RACK-TLP RFC when both Linux and MacOS implementations did fine already?
Re: Boosting upload speed and improving Windows' TCP stack
#93I had a similar issue with Windows kernels "recently" (2016~?)... I don't have the memory or patience to write a long and inspiring blog post, but it comes down to: Even with IOCP/multiple threads: network traffic is single threaded in the kernel, even worse, there's a mutex there. Putting the effective limit on PPS for windows to something like 1.1M for 3.0GHz. The task of this machine was /basically/ a connection m…
Re: Boosting upload speed and improving Windows' TCP stack
#94Has Dropbox ever experimented with SCTP or other protocols that don't enforce strict ordering of packets? I know some middleboxes struggle with SCTP (they expect TCP or UDP), but in that case you do SCTP over UDP or have a fall back.
In the future we are planing on having an HTTP/3 support which will give us pretty much the same benefits as SCTP with a better middlebox compatibility.
Re: Boosting upload speed and improving Windows' TCP stack
#95Re: Boosting upload speed and improving Windows' TCP stack
#96How come Linux doesn't have this issue? Why did Microsoft had to fix TCP with the RACK-TLP RFC when both Linux and MacOS implementations did fine already?
The linux implementation already had rapid acknowledgements and tail loss probe for a long time. I think it was prototyped there by google.
Re: Boosting upload speed and improving Windows' TCP stack
#97I lead the Windows TCP team. We blogged about recent TCP advancements which is very relevant: https://techcommunity.microsoft.com/t5/networking-blog/algor...
Are equivalents to linux' BQL/AQL, fq_codel, TCP_NOTSENT_LOWAT in the pipeline?
Re: Boosting upload speed and improving Windows' TCP stack
#98Earlier quoted context omitted.
I disagree. I had my machine backed up to Google Drive using their Backup and Sync program and when I got a new machine there was no reasonable way to restore the data from the old machine to the new machine, using Google Drive. Sure I can copy data from my old machine, but what if ti was lost or stolen? If the app can't handle this use case, what's the point of it? The only way to restore the files is in small chunk…
Are you saying the files were no longer available in Google Drive? Did you download the Drive for desktop client to try restoring files or just try reinstalling the Backup and Sync client?
Re: Boosting upload speed and improving Windows' TCP stack
#99Earlier quoted context omitted.
I disagree. I had my machine backed up to Google Drive using their Backup and Sync program and when I got a new machine there was no reasonable way to restore the data from the old machine to the new machine, using Google Drive. Sure I can copy data from my old machine, but what if ti was lost or stolen? If the app can't handle this use case, what's the point of it? The only way to restore the files is in small chunk…
To be fair it is called Backup and Sync not Backup, Sync and Restore. But on a more useful note how I have handled this in the past is to download the complete Google Drive data using Google Takeout. Not the greatest solution but it has worked.
Re: Boosting upload speed and improving Windows' TCP stack
#100Is TCP the best choice? Why not UDP?