Combining CPU's to process Work Units

Anonymous
Topic 13343

The current Einstein@Home App could easily be made multithreaded. Unlike than e.g. with CPDN, where the next stage of the model depends on the previous stage, the calculations done e.g. for a single sky position is independent of all the others, so it would just be splitting the lopp over them. However this is also the reason why running two WUs using two CPUs one after the other wouldn't be faster than running two WUs in parallel with only one CPU each. As Einstein@Home is CPU-bound instead of e.g. I/O-bound, the overhead doesn't matter much on modern systems. And last but not least this would require a heavy modification to BOINC and the way it handles CPUs.

BM