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.
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.
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)
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.
k thanks. My cpu vs run times are all over for the few mt tasks i've run. The last task I did had a larger cpu time than the run time, but the others did not. So, I have no idea how the tasks times are being recorded.
http://yafu.dyndns.org/yafu/results....state=3&appid=
I should have stopped at 100k instead of 150k and then I wouldn't feel the need to get my 250k MM.
Right. This is why I started this thread. The problem goes away with the non-MT app.
Well, if anyone has the time to create a working app_info file please post it here