[PATCH] test: split test-largefile.t in multiple file

[Mads Kiilerich]

On 05/16/2014 10:28 PM, Pierre-Yves David wrote
>>
>> I will still claim that when this makes a difference for your full test
>> suite benchmarks then it is because the test scheduler is inefficient.
>
> I curious about your scheduling algorithm that get a better outcome 
> for a 120 seconds tests case in a 2 minutes total test runs…

Ok, Matt already implemented something like that in 09e1c148e847.

After looking at your numbers, I agree it it will improve your case.

But ... you say that running the big test alone takes 60s. And when 
running it as one of 90 jobs on your 64 cores, it takes 120s even though 
it presumably is running as the only process for the last 30s. These 
numbers surprises me. Is there a bottleneck elsewhere / do the cores 
really scale that badly / are the cores really so dual-core-fake / is 90 
jobs really the optimal number?

/Mads