August is a board report month for River. There will be slight change in
procedure.
The board is concerned about projects whose reports do not change much
from month-to-month. That can mean a healthy project that is just
progressing slowly, but has a functional PMC etc. I believe that is the
I’ve wondered about doing this in the past, but for the workloads I’ve worked
with, I/O time has been relatively low compared to processing time. I’d guess
there’s some combination of message frequency, cluster size and message size
that makes it compelling.
The idea is interesting, though,
Hello,
I am wondering if anyone has looked into creating tree based algorithms for
multi-cast of RMI messages for river. Assuming a local cluster, such
patterns generally have log(p) cost for a cluster with p nodes.
For the curious, this is how many MPI messages are communicated under the
hood.
