Usually WUs on my new 5850 take ~2min - now I got some like this in the mix...
Is that intended?

just in case it's purged too quickly: de_14_3s_const_3_391634_1267691174_0
wall clock time: 17.176 seconds
Granted credit 213.759564

---

mic.

Shhhhh....they might change the credits.

I just started getting those as well since last night...right after I replaced the GTX260 with a HD5850. Was a little worried until I saw the HD4850 crunching them as well.

About 20 seconds on the HD5850 and around 45 seconds on the HD4850.

---

"Government big enough to supply everything you need is big enough to take everything you have."
-Thomas Jefferson
American Thinker

I thought I would try and get some of these, but they appear to have gone away.

Anyway, I am crunching, but only 1 WU at a time. This is despite my app_info file reading as follows -

<file_info>
<name>astronomy_0.20b_ATI_SSE2_ati.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook32.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.01</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline>n3</cmdline>
<file_ref>
<file_name>astronomy_0.20b_ATI_SSE2_ati.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook32.dll</file_name>
</file_ref>
</app_version>

</app_info>

I remember before crunching Collatz these last few months that I was able to crunch several Milkyway WUs at a time. I remember 1 WU gave a good RAC, but 2 WUs crunched at the same time gave much more and 3 at a time reduced the output.

Is it possible to remind me how I can get 2 WUs crunching together again, please?

---

Go away, I was asleep

I thought I would try and get some of these, but they appear to have gone away.

...

hmm... just got another bunch of those de_14_'s

---

mic.

Is it possible to remind me how I can get 2 WUs crunching together again, please?

Use the count tags! Example:

<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>

;-)

---

Lovely greetings, Cori

I thought I would try and get some of these, but they appear to have gone away.

Anyway, I am crunching, but only 1 WU at a time. This is despite my app_info file reading as follows -

<file_info>
<name>astronomy_0.20b_ATI_SSE2_ati.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook32.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.01</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline>n3</cmdline>
<file_ref>
<file_name>astronomy_0.20b_ATI_SSE2_ati.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook32.dll</file_name>
</file_ref>
</app_version>

</app_info>

I remember before crunching Collatz these last few months that I was able to crunch several Milkyway WUs at a time. I remember 1 WU gave a good RAC, but 2 WUs crunched at the same time gave much more and 3 at a time reduced the output.

Is it possible to remind me how I can get 2 WUs crunching together again, please?

Any more it does not matter if you crunch 1 or 2 at a time, they take an identical time.

1 at a time: 5:06
2 at a time: 10:12

No benefit at all.

---

Thanks Cori, it works.

After running 2 consecutively for a little time I have reverted to 1, just to see how things go overnight before reverting to Collatz for a while.

---

Go away, I was asleep

...
Any more it does not matter if you crunch 1 or 2 at a time, they take an identical time.

1 at a time: 5:06
2 at a time: 10:12

No benefit at all.

Not true. If you run only 1 app at a time, the GPU will sit idle between WUs. If you run 2 WUs at a time, offset, GPU will never be idle.
BR,

---

Same here, not complaining though ;o)

Got a handful of shorter ones overnight.

For example: de_14_2s_const_3_2276048_1267832764

Only took about 40 to 50 minutes instead of the normal 4 - 4 1/2 hours on my CPU.
They pay good too. But they seem to be in the minority.

---

Never surrender and never give up. In the darkest hour there is always hope.

I hope these de_14's stay around for a while as they do crunch way faster than anything else, and you can score major credits quickly, as it appears they run about 5 times faster that the usual jobs, and that is on everything, my 295's, 5870 's and i7 920's.

On Thursday, I came within 30,000 of having my first 1 million credit day, so close, and not likely to happen again as they are now sending fewer of these really fast crunching jobs. I am actually glad in a way that they are not all this fast, as just one day of nothing but these jobs would be ridiculous, and sort of spoil things by granting too many credits, as I would end up being able to earn more than 4 million credits/day. CPU's are no longer able to produce numbers that make my over-clocking them even seem worth anymore and even doing it to my GPU's is becoming too much trouble as they tend to run hot even at stock speeds and keeping everything not only cool but quiet, can take a lot of work and extra expense for just small increase.

While Milkyway is great for GPU's it is not that great for CPU's, does anyone know of a good CPU project.

---

I'm a very happy bunny at the moment :-)

I hope it keeps up

---

Don't drink water, that's the stuff that rusts pipes

I'm a very happy bunny at the moment :-)

I hope it keeps up

...the Kredit Kops will come to haunt us....

---

mic.

The Project needs to do something about people Aborting the longer Wu's and running only the Shorter ones. It's already evident some People are running scripts to abort the Long ones and run only short WU's as their output has Doubled or even Tripled.

Prime Example of running only the Short Wu's > http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=155282&offset=0&show_names=0&state=3 >>> http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=146264&offset=0&show_names=0&state=3 There are others too ...

---

STE\/E

I am afraid that it is technically quiet difficult to rectify this abuse. Honnestly, in that case I won't mind deviding the amount of credit given by these WU's by 5 to 7.

I take what I am given in workunits be they short or long. If some people are filtering out the longer ones then I think that is unfair to the rest of us that are playing straight. :-(

---

Don't drink water, that's the stuff that rusts pipes

Possible solution : Take an abort counter per user, that is reset on a daily basis to the queue length. Every abortion decreases the counter, every result resturned increases the counter. Counter below 0 = No WU ...

If I remind it correctly GPUGrid uses a similar technique...

Is this workable / realistic ?

Other solution, every infriction reported and valid = 1 week ban.

Cons : admin overhead and snitching culture ...

Reset the offending Host's to 0 and you wouldn't have the Aborting Problem anymore, at least not on the scale it is now on some Box's. There's no valid excuse for a Computer running only the Shorter Wu's other than some Script running to Abort the Longer Wu's.

They would still try to get away with what they could but couldn't just completely Abort all the longer Wu's and only run the Shorter Wu's.

---

STE\/E

Completely agree with you PoorBoy.