<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 15, 2016, at 5:23 PM, Kurt Keville <<a href="mailto:kurt.keville@gmail.com" class="">kurt.keville@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Well the first batch of nodes we are going to try this with are the Jetson TK1s... <div class=""><a href="http://www.nvidia.com/object/jetson-tk1-embedded-dev-kit.html" target="_blank" class="">http://www.nvidia.com/object/jetson-tk1-embedded-dev-kit.html</a> ... there aren't a lot of I/O options and we have already tested the onboard GigE and found it to be lacking in a couple of areas. We were thinking it would be good for intracluster commo but not a lot of sustained writes to the head node. NVidia understandably didn't put a lot of money into the NIC on board the Jetson so it isn't much to write about. There are some tantalizing GPIO pins that might represent a path to a better network although a lit search doesn't turn much up. The next gen Jetson model (the TX1) has a GPIO pinout that is compatible with Ras Pi Shield standard but I don't think that is true with the Tegra K1... That's how I ended up investigating this path; bandwidth to local disk is pretty good on these dev kits and there aren't many (better, faster, cheaper) ways to get data off these... the best picture of the <span style="color:rgb(84,84,84);line-height:18.2px" class="">µ</span>cluster so far is at ... <a href="http://web.mit.edu/~kkeville/www/Jetson3.jpg" class="">http://web.mit.edu/~kkeville/www/Jetson3.jpg</a></div></div><div class="gmail_extra"><br class=""></div></div></blockquote><br class=""></div><div>First thought is to tune the GigE port. Crank the MTU from 1500 to 9000 and it will make a huge difference in CPU usage and throughput. There’s some other kernel tunables that you can look up to make more efficient use of the memory.</div><div><br class=""></div><div>The USB 3.0 GigE port is another good idea. Then you can either bond the interfaces together or segregate the traffic over two separate networks.</div><div><br class=""></div><div>-Mark</div><br class=""></body></html>