The vm approach would require a lot of micro managing. It appears the Yafu will only let me download 4 at a time as I tried it again. So, I may have to just do the mt tasks. It may not be too bad. I just looked at some other crunchers completed tasks and it looks like they do count the total run time now for all cores.
Interesting. I took a look at some tasks, and I am seeing mostly the opposite. For example.
Run time 25,276.24
CPU time 7,437.88
Those numbers should be reversed.
Ok, so is the credit at this project based on run time or cpu time? It's hard to tell with the numbers i'm getting.
I would think an app_info.xml would solve the problem. When my 24 core web server was crunching AQUA, running more than 8 cores on a task was a waste as the cores wouldn't be fully utilized. I let it download some tasks and then used the sched_reply file as a template to create an app_info file. I changed the max and average cpus to be 8 rather than 64 so it would run one WU for every 8 cores. The same thing should work here by using just 1 cpu.
Spring 2008 Race: (1st Place)
Update:
The fact that CPU time reporting is messed up, has nothing to do with the credits awarded. Credits are based on run time and the number of threads (MT app). You can read more about it here.
Anyway, after doing some more data analysis, there is an upside. Credits awarded are not so horrible after all. On a Core2 CPU, credits range from 20-40 credits/hour/thread. Considering that the old "normal" method of awarding credits awarded ~20 c/h/t*, it is not worse than it used to be, once the machine settles down under CreditNew....at least for this project. I validated this across three different machines.
So I guess this is a long way to say it is safe to come back to yafu, if you want. It would be nice to keep our #1 spot there. Remember, it is a finite project. So we can keep that #1 forever.
*Seriously. Compare to some of the older projects like amelegrid, sztaki, etc