Yes, that score is still valid. We changed because we received reports that the old way
was complicated and we wanted to simplify. Also, the old “find” was only searching a
subset of the files so we fixed that as well.
On Nov 1, 2017, at 6:23 AM, Osamu Tatebe
It seems the git repository becomes almost completely new.
io_500_core.sh is now io500_fixed.sh.
The score using io_500_core.sh is still valid?
If there are some differences, please let us know.
On Wed, 25 Oct 2017 19:22:03 -0600
John Bent <johnbent(a)gmail.com> wrote:
> Hello Osamu,
> That's fantastic news! Did you just do it today? I'm curious because we
> have been working hard over the past two weeks to simplify the process and
> we're curious to hear how we've done.
> The submission instructions are in ./doc/README.md. Basically, you just
> create a JCAHPC_Oakforest-PACS subdirectory under ./site-configs/ and copy
> your results into there. Also please put the input script you wrote as
> well as any find tools you created. Then do a pull request against the
> github master. Sound OK?
> On Wed, Oct 25, 2017 at 7:17 PM, Osamu Tatebe <tatebe(a)cs.tsukuba.ac.jp>
>> Hi Julian,
>> We measured the IO-500 score using JCAHPC Oakforest-PACS
>> storage system. How to submit the result?
>> On Wed, 25 Oct 2017 12:23:15 +0200
>> Julian Kunkel <juliankunkel(a)googlemail.com> wrote:
>>> Dear all,
>>> at SC we'll have a BoF regarding the IO500 and the VI4IO, you'll
>>> the information + agenda here:
>>> IO-500 mailing list
>> Osamu Tatebe <tatebe(a)cs.tsukuba.ac.jp>
>> IO-500 mailing list
Osamu Tatebe <tatebe(a)cs.tsukuba.ac.jp>