Microsoft Azure also gives out 200 free credits. Which amounts to this host for 1 month.

Thanks for all the advice! You were both very helpful

Unreal!

I take it then that this was on the NT host for Rosetta? I see you encountered the ultimate long-running task there. Ran for 35hrs.

Have any other Rosetta tasks apparently had this occur?

Keep in mind that when two cores are running, you are counting it as 2 CPU seconds per second of time on your wrist watch.

So, you seem to be pointing to 50 vs 150 credits as being a 3X difference. But, because hyperthreading to two cores is recording CPU time against two tasks at a time, you should expect to see roughly a 2x difference.

So, if 1 core was getting 150 credits for a given WU run length. If I split that one into 2 HT cores, and each earns 50 credits for roughly same WU length, that's 100 credits earned in that time, because I did the same on two tasks at once. So, really, you need to be comparing 100 with 150.

And since both HT threads need floating point operations, they aren't able to run full out the way a single thread can. They also contend for the same amount of L2 cache on the CPU.

So, yes, running with HT active (i.e. 2 tasks at once) will NOT double your credit per hour. And yes, it's a bit unexpected that you didn't earn something more then 150 with two cores active. But, yes, credit between tasks varies significantly and is very difficult to benchmark. You really have to look at about a month of completed work each way to have enough data to draw any conclusions.

it's a C2D CPU - not P4/i7! ;)

Well, now I'm downloading 12 big files (from 2.13 to 12.46MB) named "homfragments_????.zip". Hopefully I'll have enough wu's until everything goes back to normal.

EDIT: Done! 12 new WU's and network activity set to "suspended". My other computer will be doing some WCG for now.