This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I've been wondering about this for a while. Is there any way to parallelize I/O operations or is this a bad idea? If you could create two lists of good and bad ways to parallelize I/O, that would be great! Thanks!
Edit: Someone please move this to the I/O forum.
Good: build a prototype that can be modified to run with various levels of parallelism. Pit it in real world system. Test and measure with real world data. Analyze results. Look for bottlenecks. Modify addressing bottlenecks. Repeat
Bad: try to design a system or come up with ideas without knowing specifics.