| |||||||||||||
git.kernel.org mirror at Googlegit.kernel.org mirror at GooglePosted Apr 25, 2012 19:26 UTC (Wed) by apoelstra (subscriber, #75205)In reply to: git.kernel.org mirror at Google by spearce Parent article: git.kernel.org mirror at Google
>Its only ~500 MiB to clone a kernel git. Clients can usually decrypt this faster than the network can transit the data.
I would expect the concern to be that the server can't encrypt fast enough to saturate its pipe. At home, I can't scp over a gigabit link at full speed (and top shows sshd pinning the CPU).
(Log in to post comments)
git.kernel.org mirror at Google Posted Apr 25, 2012 22:02 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]
Truecrypt with AES-NI turned on benchmarks at about 1Gb/sec on my Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz.
git.kernel.org mirror at Google Posted Apr 26, 2012 15:05 UTC (Thu) by spearce (guest, #61702) [Link]
>> Its only ~500 MiB to clone a kernel git. Clients can usually decrypt this faster than the network can transit the data.
> > I would expect the concern to be that the server can't > encrypt fast enough to saturate its pipe
We actually find we have sufficient server CPU to do the SSL encryption, but there is never enough bandwidth between the client endpoint and the remote server. Our servers won't permit this experiment (they require use of SSL), but doing a git clone over http:// runs at the same bandwidth as https://, as the choke points aren't the server CPU, but instead limited bandwidth on network links between client and server.
The Google side of the network is obviously shared with other services the company offers, and this bulk data transfer traffic may be prioritized lower than other data that users want immediately, such as web search results.
|
|||||||||||||