10-29-2013, 06:23 PM
VCL 1.22 has some bugs, hence the note on the VCL webpage.
the number of gpus has nothing to do with getting away with gigabit. ethernet latency is ethernet latency, regardless of how many gpus and how many nodes you have, and ethernet latency sucks.
with only 8 GB of ram on the broker you likely don't want to use a -n value of more than 80.
if the clocks are being reported incorrectly, restart the broker daemon first, then restart opencld. should fix that.
the number of gpus has nothing to do with getting away with gigabit. ethernet latency is ethernet latency, regardless of how many gpus and how many nodes you have, and ethernet latency sucks.
with only 8 GB of ram on the broker you likely don't want to use a -n value of more than 80.
if the clocks are being reported incorrectly, restart the broker daemon first, then restart opencld. should fix that.