Changes between Version 14 and Version 15 of AppMultiThread

Timestamp:

Mar 12, 2008, 2:35:52 PM (17 years ago)

Author:

davea

Comment:

--

AppMultiThread

@@ -12 +12 @@
 Possible reasons to do this:
 
- * If your application's memory footprint is large enough that, on some PCs, there's not enough RAM to run a separate copy of the app on each CPU.
- * If you want to reduce the turnaround time of your jobs (either because of human factors, or to reduce server occupancy).
+ * Your application's memory footprint is large enough that, on some PCs, there's not enough RAM to run a separate copy of the app on each CPU.
+ * You want to reduce the turnaround time of your jobs (either because of human factors, or to reduce server occupancy).
 
 Writing and debugging a multi-threaded app is hard.
 You may be able to use languages like Titanium or Cilk,
-or libraries of numerical "kernels" that are multi-threaded.
+or libraries of multi-threaded numerical "kernels".
 
 == Assumptions ==