Hi IO500 Committee,
First, thanks a ton for all of the hard work your team does! I know
this round probably didn't go the way you guys were hoping and I just
wanted to say thank you for being flexible and listening to the
community. I think you guys are probably right to consider delaying
it. It's a little rough since I just got funding approval for a larger
EC2 cluster and we got the libcephfs aiori backend working with the new
C app, but that's OK. Another month of polish would probably serve us
well too. Having said that I was all amped-up for a frantic week of
coffee, pizza, and 16 hour days of coding and benchmarks. Now I'll have
to go outside and relax or something. ;)
PS: Your plan for future iterations sounds excellent!
Mark
On 5/29/20 5:14 PM, committee--- via IO-500 wrote:
Dear IO500 Community,
We have heard your concerns about the late announcement of changes and
have already taken one concrete action and are considering a second
but we want your feedback about it first.
We are considering postponing our BoF, and our deadline, by one month.
Since we are not tied to ISC this year, we have this latitude. Are
there any objections from the community to this postponement?
For our concrete action, we will shift future schedules so that three
months from an event we release a candidate benchmark and the likely
rules set for public testing. Then commit to 6 weeks before the event
to finalize the benchmark and rules. Then things are locked until
after the event.
Please let us know how you feel about the possible postponement and
please do know how deeply we value you all in our community that makes
everything we do possible.
Based on the feedback received, we will make and announce our final
decision by EOD Sunday AOE.
Thanks,
The IO500 Committee
_______________________________________________
IO-500 mailing list
IO-500(a)vi4io.org
https://www.vi4io.org/mailman/listinfo/io-500