Hello, On Wed, Jan 9, 2013 at 5:30 PM, David Given <[email protected]> wrote: > Michai Ramakers wrote: > [...] >> ...resulting in about 70 kB/s traffic with very rare (a minute or more >> in between - didn't time exactly) single bursts. According to top(1), >> neither server- nor client-fossils seem to be doing anything >> CPU-intensive at that time. > [...] >> Both 'local to local' clones were slow (70 kB/s), while both 'remote >> to local' clones were fast (around 7 MB/s). > > My instant gut reaction here is to say 'IPv6'. If your DNS setup is > wrong on the 'local' machine, then whenever it tries to look up > localhost it could well be spending ages trying to query it up the DNS > hierarchy. This would explain the burst traffic: every HTTP connection > would involve a very long pause for the lookup, and then normal traffic > thereafter. > > I don't know if this is actually the case or not, but don't ask me how > to fix it --- I don't use IPv6 on any machines I admin. But these links > might be relevant: > > http://www.linuxquestions.org/questions/linux-networking-3/ipv6-stopping-dns-lookup-on-localhost-207066/ > > https://bugzilla.mozilla.org/show_bug.cgi?id=86449
Thank you for the suggestion, however: $ /tmp/fossil clone http://[email protected]:8080/ copy.fossil (same result - slow) Michai _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
