hgweb: tweak hgwebdir.refreshinterval to improve performance

Matt Mackall mpm at selenic.com
Mon Nov 26 11:47:43 CST 2012


On Mon, 2012-11-26 at 17:25 +0100, Markus Zapke-Gründemann wrote:
> If hgweb is serving a lot of repositories which are organized in subdirectories
> and some of them containing subrepositories a single non-bare repo can slow
> down the performance of hgweb significantly. I know it's not recommended to
> have non-bare repositories served by hgweb. But sometimes users don't listen to
> your advice.
> 
> I took a look at the code and it looks like hgwebdir.refresh reads all the
> repos which are defined in the configuration. hgwebdir.refresh waits for
> self.refreshinterval seconds until the next refresh is made. I am right that if
> self.refreshinterval could be set to a higher value this could improve the
> performance of hgweb with the cost of having slightly outdated data served by
> hgweb?

Perhaps. Or perhaps it would just take that many more months to figure
out why your hgweb performance is bad.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list