Hello Gabor, Yes, currently updateVertex only gets called when a new message was received. Could you please describe the logic behind your triangle count? The one I know is described at the beginning of page 1643 in this article: http://www.cc.gatech.edu/~bader/papers/GraphBSPonXMT-MTAAP2013.pdf
As you can see, each time(for all the three supersteps), a message gets sent. Here is my suboptimal implementation of the algorithm in the paper (it's supposed to prove that high degree nodes overload the system): https://github.com/andralungu/gelly-partitioning/commit/224cb9b6917c2320e16a657a549b2a0313aeb300 It needs some serious rebasing. I'll get to it this weekend :). Nevertheless, it should serve as a starting point for your implementation. Let us know if you have further questions! Andra P.S. I'm not sure calling vertexUpdate with an empty message iterator would be so straightforward to implement. I'll have to look into it a bit more once I get some spare time :) On Thu, Apr 16, 2015 at 9:44 PM, Hermann Gábor <reckone...@gmail.com> wrote: > Hi all, > > I am implementing a simple triangle counting example for a workshop with > vertex-centric iteration and I found that the updateVertex method only gets > called if there are new messages for that vertex. Is it the expected > behavior? > > I know that the iteration should stop for the given vertex when the we > don't change the vertex value but (at least in my case) it would be useful > if the updateVertex got called with an empty message iterator. I guess > receiving zero messages might have a meaning in other cases too, and the > user would like to update the vertex value. > Does changing the current behavior make sense? > > Cheers, > Gabor >
