Open AgustinCB opened 6 years ago
I think using par_iter everywhere may not always result in performance increase due cache/memory overhead. I think we need to consider how we implement concurrency/parrellism at an archtectural level.
There are many approaches we could take : tokio-rs, rayon, shred etc...
Implementing iterators we should remember the events must be processed in topological order in divideRounds(), decideFame() and findOrder(), according to Swirlds paper. So any implementation must not break that order.
Yeah, we should be using rayon only where order isn't relevant.
There're a lot of of
.iter
and.into_iter
that would be replaced by the alternatives proposed by Rayon. We should use it.