[issue3005] MemoryError when using highlight

Malte Helmert bugs at mercurial.selenic.com
Tue Sep 13 04:30:15 CDT 2011


New submission from Malte Helmert <malte.helmert at unibas.ch>:

(Apologies if this is directed to the wrong place. Hints on where to go
instead appreciated!)

I'm running a public Mercurial repository via hgweb.wsgi on
http://hg.fast-downward.org. I regularly got performance problems where
Apache would balloon to 3+ GB of RAM and 2x 100% CPU used. (This is a
machine with a dual-core CPU and 4 GB of physical RAM.) Occasional
MemoryErrors and some other symptoms pointed at the highlight extension as
the culprit. After disabling it, I'm now very rarely at more than 1% of CPU
and 100 MB of RAM.

There are some large files in the repository (see
http://hg.fast-downward.org/file/251a83c48971/benchmarks/openstacks-strips
-- warning, the largest files there, which are around 20 MB, crash firefox
for me!).

If highlight is indeed responsible, it would be nice if
1) performance of the extension could be improved, or
2) if it could be configured to ignore files beyond a certain size.

I can try working on a patch if there is interest.

Unfortunately I'm not at the newest versions of everything; Python,
Mercurial and Pygments are all the versions shipped with Ubuntu 10.10. I can
conduct some performance experiments with more recent versions if necessary.

----------
messages: 17412
nosy: malte
priority: bug
status: unread
title: MemoryError when using highlight

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue3005>
____________________________________________________


More information about the Mercurial-devel mailing list