[aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing

[Andrew Haley]

On 20/04/17 03:03, Zhongwei Yao wrote:
> On 19 April 2017 at 19:30, Andrew Haley <aph at redhat.com> wrote:
> 
>> Looking at this some more, I can't tell which benchmarks are
>> throughput (big is good) and which are time (small is good).  This
>> makes it very hard for me to see where community AArch64 is lagging
>> performance.
>>
>> I think Dacapo is throughput?  And TeraSort is time?
>>
>> The results for Partner B's hardware on Dacapo are so weird that I
>> think there must be something wrong.  lusearch didn't work at all, so
>> there must be a code generation problem somewhere.
> 
> On our Partner B's hardware, lusearch could run but it failed to converge
> at warmup stage at every time. So the result is set to 0 in our result.
> 
> And for sunflow case, it is in similar case like lusearch. Sunflow could
> run but it failed to converge at most time. I've checked it succeeds to
> converge only once in our result. So the standard deviation is 0 because of
> there are only one. I should have added note for this case. Sorry for
> confusion.

OK, so I think we have to reject all of the results on Partner B's hardware
because something is severely broken.

Andrew.