Slow hgweb.cgi

[Dominik Psenner]

Pushing/pulling to/from the repository directly to the samba share works
flawless and goes through in a jiffy. Doing the same pull without changes
takes a total of about 16 seconds.

hg --repository XXX-hg pull --verbose --update --config
ui.merge=internal:fail --debug http://hgserver/hg/XXX/
using http://hgserver/hg/XXX/
sending between command << about 4secs in here
Hole von http://hgserver/hg/XXX/
sending heads command << about 4secs in here
Suche nach Änderungen
Keine Änderungen gefunden
checking for updated bookmarks
sending capabilities command << about 4secs in here
capabilities: changegroupsubset stream=1 lookup pushkey
unbundle=HG10GZ,HG10BZ,HG10UN branchmap
sending listkeys command << about 4secs in here

So the server takes nearly constantly 4seconds to respond on each command
sent. Ideas?

> -----Original Message-----
> From: Patrick Mézard [mailto:pmezard at gmail.com]
> Sent: Tuesday, April 12, 2011 2:52 PM
> To: Dominik Psenner
> Cc: 'Mercurial Developers'
> Subject: Re: Slow hgweb.cgi
> 
> Le 12/04/11 14:17, Dominik Psenner a écrit :
> > Hi guys,
> >
> > we're experiencing really slow push/pull performance while using a
> > apache/hgweb.cgi repository publishing with wscgi. It takes almost a
> full
> > minute to pull 2 of changesets with a diff size of only 4kb! If I do a
> > simple hg incoming it also takes a long time.
> >
> > The repository server is a headless ubuntu vm and the repository data is
> > physically stored on another server and accessed with cifs/samba. The
> > mercurial version we run is 1.6.3 from the ubuntu 10.10 default
> > repositories. I also observed that the python script invoked by apache
> peaks
> > to use one core of the server completely. So unfortunately the long wait
> > times are on the server side.
> >
> > Could the cifs/samba storage cause the problems?
> >
> > Or have you any ideas what could speed it up? I could even go and
> > troubleshoot for problems if one tells me how.
> 
> Is it slow if you push to the server locally, bypassing the wsgi setup?
> 
> If not, try pushing remotely with --debug, it should display the different
> steps taken to push stuff and make the problem more obvious.
> 
> --
> Patrick Mézard