run-tests.py refactor
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Sat Apr 26 15:43:00 CDT 2014
On 04/25/2014 06:10 AM, Martin Geisler wrote:
> Gregory Szorc <gregory.szorc at gmail.com> writes:
>
>> On my i7-2600K mech HD w/ -l -j8:
>>
>> Original:
>>
>> real 6m40.558s
>> user 31m31.405s
>> sys 17m48.862s
>
> I normally run with -j 20 and get a real time of 4m24s. I find that
> there's so much IO going on that I can start that many processes in
> parallel to really saturate the CPU (maybe -j 15 would be the same).
My best result is 1m 49s:
* running test in/dev/shm
* using -j 90
* on a 64 core power7
On firefly on /dev/shm I'm around 2m 30s
At that point the main issues are the longuest test.
--
Pierre-Yves
More information about the Mercurial-devel
mailing list