bitbucket: 1.3 minutes to ask password, and 8 minutes to find out it is wrong ??

[Augie Fackler]

On Jun 19, 2011, at 9:41 AM, Mads Kiilerich wrote:
> 
> Andreas Tscharner wrote, On 06/19/2011 04:08 PM:
>> On 19.06.2011 15:00, Mads Kiilerich wrote:
>>> rupert.thurner wrote, On 06/19/2011 01:19 PM:
>>>> when doing an initial push to an empty bitbucket or google mercurial
>>>> repository it takes nearly 10 minutes to get an "authorization
>>>> failed". only until mercurial asks the password one has to wait for
>>>> more than a minute.
>>> 
>>> Obviously it works fine for everybody else. There must be something
>>> different between your setup and other setups. Please work
>>> systematically try to figure out what that could be - perhaps by trying
>>> to reproduce on another machine on another network connection - and
>>> perhaps another OS.
>> 
>> I did that just today and I can confirm that behavior. 
> 
> 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 http://mercurial.selenic.com/bts/issue1876 . That is no problem with small pushes or high bandwidth, but the opposite combination is worse.

If you can update the server to a development snapshot and enable ui.usehttp2 on the client, this double-sending of data should go away in most/all situations.