It has been fun, while it lasted! I for one can no longer justify the electricity consumption to have my computer running 24-7. My credits went from 1200+ to 400- 500 a day. Good Luck!

Geez Rick, install the optimised app and watch your credits get over 2000 per day.....

My old 3.0GHz P4 currently has a RAC over 1700 and rising while still doing other projects

Regarding flocking to the project

These are statistics, gleaned a few moments ago, from BOINCstats.

Active BOINC user in the last 60 days: 321,562 using 561,867 hosts

Of these, those who calculate for MilkyWay in the last 60 days: 3,276 using 8,574 hosts.

Only 1.019% of users calculate for MilkyWay
Only 1.526% of computers calculate for MilkyWay

It can not even be unreasonably argued that people are flocking to MilkyWay to earn credits.

-ChinookFöhn

If the science is worth while, then the project will have very little problem getting crunchers anyway. The kredit kops are always saying that those of us who crunch for competition are in the minority, so why is there so much concern for credit parity? If we are the minority, then it should not matter to the projects if we credit shop because the majority of crunchers are doing it for the science and care less about the credits. This whole parity thing still does not make sense to me. Let each project set their own credit level as they want it and let the "minority" shop for credits if they want to.

Only a fair competition is a valid competition.
If the credit thieves poison the competition with unjustifiable high credits they should stop exporting them in the BOINC framework, as the credits here for example have nothing in common with the other BOINC projects.

Make the XML useless for Willy, Zain, James and Co, and the competition can go on within MW and within the projects that follow the BOINC intentions. A "competition", where you can get the same credits for nothing (here) like everywhere else for real work is not such, it's just a farce.

---

Grüße vom Sänger

... A "competition", where you can get the same credits for nothing (here) like everywhere else for real work is not such, it's just a farce.

Is crunching more in less time "nothing"? Don't really think so.
And besides it's not uppercases WUs here... *grin*

---

Lovely greetings, Cori

... A "competition", where you can get the same credits for nothing (here) like everywhere else for real work is not such, it's just a farce.

Is crunching more in less time "nothing"? Don't really think so.
And besides it's not uppercases WUs here... *grin*

Cori, I second your statement !

All the best,

Kurt

---

A "competition", where you can get the same credits for nothing (here) like everywhere else for real work is not such, it's just a farce.

The beauty of removing all "credit limits" from the sphere of influence of BOINC or any of the projects is that the projects no longer have to put up with the administrative overhead of these arguments amongst participants.

There are two solutions, both of which need a freezing of current credits and starting out everyone at zero again:

1) Only have competition within a project, not between projects.

2) Let the stats sites be the arbitrators of credit exchange rates and cross-project rankings WITHOUT the influence of BOINC administration and people who continually harp on the projects that pay out more than SETI, but do not go after the projects that pay out less than SETI with the same zeal.

Only a fair competition is a valid competition.
If the credit thieves poison the competition with unjustifiable high credits they should stop exporting them in the BOINC framework, as the credits here for example have nothing in common with the other BOINC projects.

you ever checked if you already have been a prayer wheel in some of your former lives?

if not, you are doing your very best this time...

Gentlemen, please refrain, this is not necessary....

---

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

you ever checked if you already have been a prayer wheel in some of your former lives?

I always have this feeling when the credit jerks start wrecking the next project with their calls for unfairness, and that their lovely credit-for-nothing-reserve is going to be normal again start their screaming and shouting.

---

Grüße vom Sänger

you ever checked if you already have been a prayer wheel in some of your former lives?

I always have this feeling when the credit jerks start wrecking the next project with their calls for unfairness, and that their lovely credit-for-nothing-reserve is going to be normal again start their screaming and shouting.

then it will be easy for you to explain to all those guys out there you're humbly adressing as *erks, why you and those other parity preaches never show up on low-paying projects to enlight the dark corners of BOINCworld with your ever so polite emissions..

Where is the optimized app? Will it work with vista/and AMD

Where is the optimized app? Will it work with vista/and AMD

look down for Milksop's post about a new app.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Where is the optimized app? Will it work with vista/and AMD

look down for Milksop's post about a new app.

Yup, it's here: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=433&nowrap=true#5789 :-)))

---

Lovely greetings, Cori

I posted this earlier, but it seems appropriate for here:

The interesting thing about WUs waiting to send, when they are available to download, is there in no point in extending the cache. There is a 20 WU per core/CPU cache limit which the system will not stray beyond.

Best have a back up project running concurrently

The thread about the optimized application being released has the link to it.

And yes it will work with Vista and AMD's. In my farm I have three iterations of Vista and AMD's (XP5000BE, Phenom 8250, Phenom 9600BE).

---

Right -- all the workstations in my farm run at least three applications -- and with the new limits it makes a lot of sense to do that.

That being said, keeping the MilkyWay cache filled seems to take a bit more hand holding than it should.

I posted this earlier, but it seems appropriate for here:

The interesting thing about WUs waiting to send, when they are available to download, is there in no point in extending the cache. There is a 20 WU per core/CPU cache limit which the system will not stray beyond.

Best have a back up project running concurrently

---

Well, I'm not going to lower my res share or anything. With this box I make a downright scary amount of credit no matter what I crunch, and besides, I like the science. But I do think I'm reaching the cap, I'm running four projects (with equal res shares) but MW has built up a huge negative debt due to running out of work a few times...