| | |
Multi-threading Vs. Distributed Computing
![]() |
Which is better?
We're designing a new autonomous robot for the competition we attend during the summer and this is one of our topics for design. I want to do a dual-processor, multi-core computer to run the software. Some others want to do distributed computing (between two laptops). Am I wrong in thinking the performance of multi-threading far outweighs that of distributed computing?
We're designing a new autonomous robot for the competition we attend during the summer and this is one of our topics for design. I want to do a dual-processor, multi-core computer to run the software. Some others want to do distributed computing (between two laptops). Am I wrong in thinking the performance of multi-threading far outweighs that of distributed computing?
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
That would be nice, but both computers have to be directly mounted to the robot. That does bring up a good point though; one that was discussed yesterday. Another pro to having dual computers would be a fail-over system.
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
How are you proposing to divide up the work between 2 laptops (if that's the way you go)?
One for each side, so each has one eye, arm, and one side of wheels?
Or one for all input sensors, and another for all movement?
Or maybe something else, say either could do any job based on current work load?
A single multi-core CPU would probably mean you wouldn't have to worry about say load balancing. And inter-process communication is fast and easy.
I'm not sure there's a "killer" argument which favours one or the other.
What about other non-computational requirements, like battery life or weight?
One for each side, so each has one eye, arm, and one side of wheels?
Or one for all input sensors, and another for all movement?
Or maybe something else, say either could do any job based on current work load?
A single multi-core CPU would probably mean you wouldn't have to worry about say load balancing. And inter-process communication is fast and easy.
I'm not sure there's a "killer" argument which favours one or the other.
What about other non-computational requirements, like battery life or weight?
![]() |
Similar Threads
- :-) C++ Developer - Financial / Trading company London, Permanent, London (Software Development Job Offers)
Other Threads in the C++ Forum
- Previous Thread: QT XML compiling error on Mac
- Next Thread: C++ debug macro
| Thread Tools | Search this Thread |
anyfile api array based binary bitmap c++ c/c++ char class classes code coding compile console conversion count delete deploy desktop developer directshow dll download draw dynamic dynamiccharacterarray email encryption error file forms fstream function functions game gdi+ givemetehcodez gnu graph gui homeworkhelp homeworkhelper http iamthwee ibm ifstream input int integer java lib linkedlist linker loop looping loops map math matrix memory multiple news node number numbertoword output packing parameter pointer problem program programming project python random read recursion reference rpg string strings temperature template test text text-file tree url variable vector video visualc++ visualizationtoolkit win32 windows winsock word wordfrequency wxwidgets






