My screen freezes at random for 2-3 mins at a time. I tried detaching and I tried switching to the WHQL Driver. The wu's will run and complete in between the freezes. I have run the ATI app before with no errors. Could the new type of wu's be causing this?

There looks to be a nice flow of wu's and I can't run them. D'oh.

Win 7 64bit, ATI 4830, Milkyway_0.19f_ATI Win64, BOINC 6.6.36 64bit

>Someone will soon come along and complain that they can not get work
Which is what took up much of the first thread...
>allows you to create an account why there is no work.
Of course no other boinc project has ever had no work... [/sarky]
On CPDN atm, we have all the work we want but can't upload any results due to the server running out of disk... again.

Sicituradastra. has 10.000.000 in MW ;-)

Way to go!

Congrats to SUSA and to CampaignForLiberty who is the ONE to make it possible.
142M of 332M points

Just in time for another challenge on milkyway_GPU !

I would be happy even with a spinning 3d model of the our galaxy..(the Milkyway) That could maybe update itself from what the project finds.

Looks like the searches are stopped, we'll not do 3 stream runs until the ATI code is fixed :)

Here is another project that you can sign up for :)

Vanderbilt BOINC

I am sure there are more if you look hard enough. :)

Maybe next time you can link to a living project.
That one has not been updated in over a year.

The home page suggests that people use the link I used to add the project in the Boinc Client.

The point poeple seem to be missing here is that there actually is a GPU home page!

It suggests people sign up and it even gives people the link to the non-active project.

I posted the errors so that the author could have a look at the HTML and fix it!

I also wanted people to know that the project is not yet live yet,

This was not an open invitation for smart mouths to stick their necks out and lip off.

Although already registered with the MilkyWay project I had to re-register - I would have preferred not to do this. I would have liked the project to respect existing users in the same way other projects do.

Can we maybe stop the GPU vs. CPU snipping, please, and keep the focus on server efficiency and performance? We understand the GPU-CPU differences of opinion, and IMO that "discussion" is at a stalemate.

Thank you.

Can't get any tasks from MW today. :(

Why not make it 120? 600, 6000...
At what point would faster CPU's start starving under normal conditions. I'm not worried about GPU burning through tasks in seconds as this is the CPU project. Would it not be a good idea to shift work toward CPU hosts being able to pick them up, at the expense that gpu can't get new tasks every minute?

My understanding is server connot distiguish cpu/gpu app with current layout. So to stop GPU cruching on main entire new app would be required. This is why GPU tasks not receive credit here when GPU project go live.

We've had server outages and some workunit problems so i'm not sure if thats representative of the situation.

Unfortunately the 'Deferring Communication for 1min' isn't a forceful measure - it can still be overridden by clicking update. The setting in BOINC is the one where the server detects if two connections are within X seconds, then it disables the second and says 'Go away for another X seconds'.

Now I'm off to figure why my i7 machine is only getting 1 WU a time =P

The bottom line is that MilkyWay@home is under a scripters' DoS attack that is reducing the total possible work throughput, and thus reducing the total science that could be done.