Mercurial > hg
view tests/helpers-testrepo.sh @ 31467:08ecec297521
bdiff: use Python memory allocator in fixws
Python has its own memory allocation APIs. For allocations
<= 512 bytes, it allocates memory from arenas. This means that
average small allocations don't call the system allocator, which
makes them faster. Also, arena allocations cut down on memory
fragmentation, which can matter for performance in long-running
processes.
Another advantage of using the Python memory allocator is that
allocations are tracked by Python. This is a bigger deal in
Python 3, as modern versions of Python have some decent built-in
tools for examining memory usage, leaks, etc.
This patch converts a trivial malloc() + free() in the bdiff code
to use the Python allocator APIs. Since the object being
operated on is a line, chances are it will use an arena. So,
this could have a net positive impact on performance (although
I didn't measure it).
author | Gregory Szorc <gregory.szorc@gmail.com> |
---|---|
date | Thu, 09 Mar 2017 11:54:25 -0800 |
parents | 3c9066ed557c |
children | 6c113a7dec52 |
line wrap: on
line source
# The test-repo is a live hg repository which may have evolution # markers created, e.g. when a ~/.hgrc enabled evolution. # # Tests are run using a custom HGRCPATH, which do not # enable evolution markers by default. # # If test-repo includes evolution markers, and we do not # enable evolution markers, hg will occasionally complain # when it notices them, which disrupts tests resulting in # sporadic failures. # # Since we aren't performing any write operations on the # test-repo, there's no harm in telling hg that we support # evolution markers, which is what the following lines # for the hgrc file do: cat >> $HGRCPATH << EOF [experimental] evolution=createmarkers EOF