- Mar 26, 2011
- 4,310
- 8
- 81
I'm not sure about the "smaller". Systems with more ram could hold larger chunks and are generally newer, faster systems with more cores that will return WUs quicker. So the projects most important to them will go to these systems and have very short deadlines to get the results back soonest so they can send the next WU out and get it back faster (remember that the next in line WU is created from returned results). If the line is 100 WUs long, quick returns makes a huge difference.
Return in one day versus return in five days is 100 vs. 500 days to find a possible cure. (Uniprocessor client WUs can have deadlines on the order of 30 or 60 days or more?) So as soon as a short deadline WU is returned, a new WU is created and sent out to the next qualified computer needing another WU. If a 16-core system needs another WU and there is no "special" WU to send the server sends something else. It works the same for your 8-core system.
Also, there is priority set for each project so some fast 8-core systems will get other projects. Imagine a researcher begging the priority setter to give his project higher priority than another researcher!?! So the server will send this one for 10 minutes & and the next for 5 minutes & the next for 20 minutes. What you get depends on where in the priority "steps" the server is.
Same for me!
After 7+ years of folding (4+ years doing a daily F@H stats thread) I decided to explore BOINC a little more. Now I am having fun trying to get many projects over different Milestones.
I'm interested.
I've never run any of the BOINC projects/clients, though they do seem interesting and I've read about them. I've heard they use a lot of internet bandwidth, though, right? My connection right now is less-than-ideal.

