Erratic and slow hgweb performance compared to a windows network share

[Angel Ezquerra]

On Tue, Jul 10, 2012 at 12:54 PM, Benoît Allard <benoit at aeteurope.nl> wrote:
>
>
>> -----Original Message-----
>> I just had a few users come to me asking whether the server is down.
>> It seems that another user is doing a big push of a brand new subrepo
>> which contains a few big files and this has blocked every other user
>> trying to access the server. Looking at the windows task manager I see
>> that httpd.exe's CPU usage is around 25%, while its memory usage is
>> 160 MB. No other process is taking any significant amount of CPU. The
>> Apache tomcat6.exe process is the one that is taking the highest
>> amount of memory, but that is only 595 MB.
>>
>
> Mercurial in itself has a few locks to prevent among others multiple write operation at the same time. Last time I looked at it, there was two kinds of locks: read locks (can have multiple of them, but not compatible with write lock), and write locks (only one allowed, not compatible with read locks.)
>
> If a user of yours is performing a huge push, I would expect the write lock to come in place, preventing anyone to read that repository until the push is done.
>
> This is anyway nothing web server related, and is this is your problem you probably had it through file share also.
>
> Regards,
> Benoît.

Yes,

the problems happen when users are accessing different repositories,
so I do not think that they are due to these repository-level locks...
(I may be wrong though).

In particular, accessing the repository list should be a read only
operation, and that slows down and even halts while a pull or push
operation is being performed.

Angel