<div class="gmail_quote">On Sun, Jun 19, 2011 at 16:41, Mads Kiilerich <span dir="ltr"><<a href="mailto:mads@kiilerich.com">mads@kiilerich.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Andreas Tscharner wrote, On 06/19/2011 04:08 PM:<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 19.06.2011 15:00, Mads Kiilerich wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
rupert.thurner wrote, On 06/19/2011 01:19 PM:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
when doing an initial push to an empty bitbucket or google mercurial<br>
repository it takes nearly 10 minutes to get an "authorization<br>
failed". only until mercurial asks the password one has to wait for<br>
more than a minute.<br>
</blockquote>
<br>
Obviously it works fine for everybody else. There must be something<br>
different between your setup and other setups. Please work<br>
systematically try to figure out what that could be - perhaps by trying<br>
to reproduce on another machine on another network connection - and<br>
perhaps another OS.<br>
</blockquote>
<br>
I did that just today and I can confirm that behavior. <br>
</blockquote>
<br></div>
Ok, as Augie hinted I wasn't completely right. Pushing over http(s) works fine for others, with the caveat that the posted data has to be uploaded twice - as described on <a href="http://mercurial.selenic.com/bts/issue1876" target="_blank">http://mercurial.selenic.com/<u></u>bts/issue1876</a> . That is no problem with small pushes or high bandwidth, but the opposite combination is worse.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I moved a small repository (~150 commits, thg transferred about 12 MiB data) to BitBucket. When I pushed, the transfer started and it took a while (I didn't use a stop watch, but I'd say it was a minute) before thg asked for username and password. During this time the transfer was paused. After I provided the information, the transfer resumed.<br>
</blockquote>
<br></div>
How could you see that the transfer paused / resumed? Didn't you see full network utilization all the time?<div class="im"><br></div></blockquote><div>my impression was that "search for changes" takes especially long when the bitbucket repository is still empty.</div>
<div> </div><div>rupert</div><div><br></div></div>