News for hackers. Stuff that matters.
Re:The Myth of Multitasking by seanstickle on Tuesday November 02, 2010 @03:48PM (#1862012)
Let's say you have three projects, A, B, and C. Assume each one takes 3 days.

You can work on them serially:

A A A B B B C C C

Or multitask them:

A B C A B C A B C

If you take a look at when the projects complete, you'll see that, in the serial approach:

A finishes on day 3. B finishes on day 6. C finishes on day 9.

In the multitasking approach:

A finishes on day 7. B finishes on day 8. C finishes on day 9.

This results in lower system throughput.

There may be reasons for multitasking, but increasing system throughput isn't one of them.

Re:The Myth of Multitasking by silvestrov on Tuesday November 02, 2010 @04:41PM (#1862257)
The throughput is the same: 3 jobs in 9 days.

You mistake the thoughput for the latency. The latency is smaller (less time from start to end) in the AAABBBCCC approach.

The reason ABCABCABC can be slower in a computer is that context switches takes time, and AAABBBCC has only 2 context switches whereas ABCABCABC has 8.

Re:The Myth of Multitasking by seanstickle on Tuesday November 02, 2010 @05:04PM (#1862342)
Slower in a computer, slower yet in people.

And the throughput in AAABBBCCC is 1 project in 3 days, where ABCABCACB has a throughput of 0 projects in 3 days. In a business where cashflow is important, that 3 day throughput is more important than the overall 9-day throughput.

Re:The Myth of Multitasking by SkyMarshal on Tuesday November 02, 2010 @06:36PM (#1862720)
That's a good point, if you're taking into account cash flow and exponential return on cash flow, then having projects finish sooner and start generating cash flow and interest sooner is preferred. Fewer context switches also contributes to that.