[Beowulf] Help with inconsistent network performance
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Peter St. John peter.st.john at gmail.comWed Dec 19 08:28:50 PST 2007
- Previous message: [Beowulf] Help with inconsistent network performance
- Next message: [Beowulf] Help with inconsistent network performance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brendan,
I'm a day late but maybe not a dollar short :-) When I read the original
question, I was going to ask, "do the compute (render) nodes push their
results when ready, or does the head (view) node pull?" and from the
subsequent discussion and clarifications it seems to be the former. And yeah
what Mark said.
So if it were me, each compute node would send the (short) message, "I'm
ready"; the head node would maintain a list of ready nodes, and pull from
them sequentially ("Ok node number 7, upload now please"). That way the only
collision is word-sized and not image-sized, and the overhead is trivial.
But that would be me using FTP and tcsh :-) Dunno what you'd do
specifically with the software you have.
Peter
> (Hahn)
> it's the _timing_ of the data. using bcast, you attempt to cause the
> render nodes to, as simultaneously as possible, saturate their own
> links, and therefore (N-1)-times oversaturate the viewer link.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.scyld.com/pipermail/beowulf/attachments/20071219/6d698c40/attachment.html
- Previous message: [Beowulf] Help with inconsistent network performance
- Next message: [Beowulf] Help with inconsistent network performance
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
