No, as far as I can tell the servers are operating normally. From home, I can checkout webkit in 30 minutes, which is of course very close to the servers, but not much closer than Mountain View. My home trace does not seem to go through Level 3, so maybe its a 3rd party network issue. I've tried to tweak the servers to compensate but nothing has made a difference so far.
Does anyone get decent download speed from svn besides me? -Bill On Mar 15, 2012, at 3:06 PM, Ryosuke Niwa wrote: > Do you know what is causing the issue? > > - Ryosuke > > On Thu, Mar 15, 2012 at 2:43 PM, William Siegrist <wsiegr...@apple.com> wrote: > Thanks everyone for the debugging information. We are working on both > hardware and software solutions, but I have no ETA to give you. > > -Bill > > > > On Mar 15, 2012, at 2:05 PM, Levi Weintraub <le...@google.com> wrote: > > > Likewise in Mountain View... it's making WebKit gardening impossible :( > > > > On Thu, Mar 15, 2012 at 2:03 PM, Dmitry Titov <dim...@chromium.org> wrote: > > over here in Seattle I am getting 5KiB/s all day, no way to get an updated > > checkout today :-( > > > > > > On Thu, Mar 15, 2012 at 10:54 AM, Jarred Nicholls <jar...@webkit.org> wrote: > > Well I was just about to follow up that from the east coast on Comcast > > bbone, I'm pulling at acceptable rates from git.webkit.org, ~700KiB/s. > > That's about as fast as it's always been. Same goes for nightly.webkit.org. > > > > There's a number of possible issues that would result in slow response > > times and slow downloads. E.g., it could be sheer packet loss between > > carrier backbones and not necessarily tapped bandwidth. > > > > > > On Thu, Mar 15, 2012 at 1:45 PM, > Ryosuke Niwa > Software Engineer > Google Inc. > > > <rn...@webkit.org> wrote: > > I don't really think checking the latency is interesting. What's killing us > > is bandwidth. As far as I tested yesterday, the ping at my work (Google SF > > office) gives me a reasonable time as well. > > > > There's something that's killing our bandwidth. Does anyone know some tools > > to investigate this? > > > > - Ryosuke > > > > > > On Thu, Mar 15, 2012 at 10:40 AM, Jarred Nicholls <jar...@webkit.org> wrote: > > Ditto, @ ae-11-70 attempting to get to ae-21-60 the trace dies. Pings to > > svn.webkit.org succeed in acceptable times however, for me. Perhaps the > > hops following ae-11-70 and ae-21-60 simple aren't able to reply with > > proper ICMP packets; no real conclusion to based on that info alone, but > > maybe worth passing off to the provider and/or directly to Level3. > > > > Jarred > > > > > > On Thu, Mar 15, 2012 at 1:22 PM, Levi Weintraub <le...@google.com> wrote: > > Likewise, I lose everything past *.car1.sanjose2.level3.net. SVN updates > > are dog slow :( > > > > 6 pr01-xe-8-2-0.sjc07.net.google.com (72.14.218.230) 4.306 ms 4.966 ms * > > 7 xe-11-1-0.edge2.sanjose3.level3.net (4.79.40.153) 20.116 ms 3.031 ms > > 3.056 ms > > 8 ae-31-90.car1.sanjose2.level3.net (4.69.152.203) 4.316 ms > > ae-11-70.car1.sanjose2.level3.net (4.69.152.75) 4.239 ms > > ae-21-60.car1.sanjose2.level3.net (4.69.152.11) 4.545 ms > > 9 * * * > > 10 * * * > > 11 * * * > > > > > > On Thu, Mar 15, 2012 at 7:31 AM, Philip Rogers <p...@google.com> wrote: > > Bill, > > > > I'm currently pulling from svn.webkit.org at what feels like 5kbps, and > > poor http://build.webkit.org/console hits the page refresh before it's even > > able to render to the bottom :( > > > > Below is a traceroute to webkit.org: > > traceroute to svn.webkit.org (17.254.20.241), 30 hops max, 60 byte packets > > 1 DD-WRT (192.168.2.1) 0.233 ms 0.297 ms 0.371 ms > > 2 10.1.10.1 (10.1.10.1) 2.446 ms 2.445 ms 2.518 ms > > 3 96.176.191.1 (96.176.191.1) 24.451 ms 25.398 ms 28.688 ms > > 4 xe-11-0-0-0-sur01.a2atlanta.ga.atlanta.comcast.net (68.85.91.177) > > 14.588 ms 15.541 ms 15.733 ms > > 5 xe-2-1-3-0-ar01.b0atlanta.ga.atlanta.comcast.net (68.86.106.57) 16.563 > > ms 16.929 ms 16.946 ms > > 6 pos-3-6-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.93.201) 17.967 ms > > pos-3-5-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.93.125) 14.599 ms > > 11.428 ms > > 7 4.28.24.77 (4.28.24.77) 15.973 ms 17.858 ms 17.307 ms > > 8 vlan51.ebr1.Atlanta2.Level3.net (4.69.150.62) 19.688 ms > > vlan52.ebr2.Atlanta2.Level3.net (4.69.150.126) 14.891 ms > > vlan51.ebr1.Atlanta2.Level3.net (4.69.150.62) 15.116 ms > > 9 ae-73-73.ebr3.Atlanta2.Level3.net (4.69.148.253) 14.651 ms > > ae-63-63.ebr3.Atlanta2.Level3.net (4.69.148.241) 13.767 ms > > ae-73-73.ebr3.Atlanta2.Level3.net (4.69.148.253) 14.955 ms > > 10 ae-7-7.ebr3.Dallas1.Level3.net (4.69.134.21) 34.004 ms 36.807 ms > > 34.950 ms > > 11 ae-3-3.ebr2.LosAngeles1.Level3.net (4.69.132.77) 66.601 ms 65.766 ms > > 66.692 ms > > 12 ae-6-6.ebr2.SanJose5.Level3.net (4.69.148.202) 78.577 ms 78.007 ms > > 78.175 ms > > 13 ae-1-100.ebr1.SanJose5.Level3.net (4.69.148.109) 78.594 ms 78.520 ms > > ae-5-5.ebr4.SanJose1.Level3.net (4.69.148.142) 81.371 ms > > 14 ae-34-34.ebr2.SanJose1.Level3.net (4.69.153.33) 71.989 ms > > ae-5-5.ebr1.SanJose1.Level3.net (4.69.148.138) 77.341 ms > > ae-34-34.ebr2.SanJose1.Level3.net (4.69.153.33) 77.662 ms > > 15 ae-62-62.csw1.SanJose1.Level3.net (4.69.153.18) 80.375 ms > > ae-61-61.csw1.SanJose1.Level3.net (4.69.153.2) 87.895 ms > > ae-81-81.csw3.SanJose1.Level3.net (4.69.153.10) 77.137 ms > > 16 ae-31-90.car1.SanJose2.Level3.net (4.69.152.203) 77.660 ms > > ae-41-80.car1.SanJose2.Level3.net (4.69.152.139) 78.313 ms > > ae-21-60.car1.SanJose2.Level3.net (4.69.152.11) 77.746 ms > > 17 * * * > > 18 * * * > > 19 * * * > > 20 * * * > > 21 * * * > > 22 * * * > > 23 * * * > > 24 * * * > > 25 * * * > > 26 * * * > > 27 * * * > > 28 * * * > > 29 * * * > > 30 * * * > > > > Thanks for looking into this. > > Philip > > > > On Thu, Mar 15, 2012 at 10:23 AM, William Siegrist <wsiegr...@apple.com> > > wrote: > > Our network provider did not find anything wrong. If anyone is currently > > seeing slow download times, I would like to see a traceroute to the server. > > > > Thanks, > > -Bill > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > > > > > _______________________________________________ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
