Permalink
Browse files

cleanup

  • Loading branch information...
1 parent 8f43655 commit eba99e0bf7770750ce26c9dba46cf2847a2be5cb Mark Pollack committed Aug 4, 2011
Showing with 1 addition and 1 deletion.
  1. +1 −1 picalc-rabbitmq/README.md
View
2 picalc-rabbitmq/README.md
@@ -4,7 +4,7 @@ This demo is an adaptation of the [Akka Getting Started Tutorial](http://akka.io
The demo consists of two web applications. The first is named 'picalc-master' and the second is named 'picalc-worker'.
-The master application takes input from a form specifying the number of parts to split up the calculation. The master sends a message for each part of the calculation to a Task Queue. Workers consume messages from the Task Queue and reply with the result to a Result Queue. The Master reads from the Result Queue, aggregates all the individual calculations, and displays the result.
+The master application takes input from a form specifying how to divide up the calculation into multiple parts. For each part of the calculation, the master sends a message to a Task Queue. Workers consume messages from the Task Queue and reply with the result to a Result Queue. The Master reads from the Result Queue, aggregates all the individual results, and displays the final result.
The advantage of this architecture is that you can parallelise the work by adding more workers. This is because each worker will take messages from the Task Queue and process them concurrently. Using the vmc command 'vmc instances picalc-worker 4' you can vary the the number of worker process. (In this case, to 4). To maximize the effect of scaling up, each worker is single threaded.

0 comments on commit eba99e0

Please sign in to comment.