Anonymous user
Talk:Checkpoint synchronization: Difference between revisions
→Ruby code does wrong task?: new section
No edit summary |
(→Ruby code does wrong task?: new section) |
||
Line 7:
Is 'checkpoint synchronization' the best name for this task? On wikipedia, there's an article ( http://en.wikipedia.org/wiki/Barrier_(computer_science)#Threads_synchronization_primitive ) which seems to fit the description of this task.
== Ruby code does wrong task? ==
I added a Ruby example. Like the Perl code, the Ruby code uses blocking IO on sockets to synchronize the workers. I am not sure if my Ruby code does the correct task. When the workers finish a mechanism, they do not immediately start to build the next mechanism. Instead, all workers wait until the main thread orders the next mechanism. While they wait, the main thread can add or remove workers. Thus, workers can only join or leave the workshop ''between mechanisms'', while all workers are idle. --[[User:Kernigh|Kernigh]] 06:09, 19 February 2011 (UTC)
| |||