I just completed a Windows 6.55 wu that had a time per step of 181ms! This is up from 136ms for my previous worst case and 103ms typically on my (9600GT). Overall time was 25 hrs for a credit of 2933. This is compared to 23 hrs for 3232 credits.

This sucks the big one!

You have to compare same WUs, I got meanwhile only four valid 2932-Point-WUs (210428, 208326, 201276, 188467), they need +90-92% more calculating time in relation to the 3232-WUs (52ms vs. 27ms with GTX 260/216, 57ms vs. 30ms with GTX 260/192, see my posting). Using 6.4.5/6.5.0.

Do you really think it´s a matter of the BOINC-version ?

What I'm getting at is the large difference in credits per hour. It makes people want to abort the poor paying wu's.....

I don´t matter about "selecting" WUs, take them as they come along, analyzing my task-list (1) I see a well-balanced mix of WUs, can´t complain about clearing the "rubbish."

Up to now, I think the problem is observed by the admins, the project deserves sympathy and participation, some troubles you can find in any other project.

Perhaps aborting WUs should be faced with reducing the limit of max WUs per day, could be a efficient method to slow down point-chasers.

I don´t matter about "selecting" WUs, take them as they come along, analyzing my task-list (1) I see a well-balanced mix of WUs, can´t complain about clearing the "rubbish."

Up to now, I think the problem is observed by the admins, the project deserves sympathy and participation, some troubles you can find in any other project.

Perhaps aborting WUs should be faced with reducing the limit of max WUs per day, could be a efficient method to slow down point-chasers.

Would also be an efficient way to stop users with 2 or 3 cards in their host from getting enough work to use all they have....yes that would be a smart move! Especially now with a GTX295 if you have 2 of those you will run out of work with the current 15 per day limit! They need to up the limit not lower it!

............. and if the project needs the science, the science needs the point chasers. Limit is already too low for some hosts. How do you think your proposal would fit with the 4 GPU machine the project team has built and the GTX295 based machine is considering building? There will always be aborts.

and if you are talking about reducing by 1 the task limit for every abort it will do no good.....there is an easy workaround for that...if you set your host to nnw then download and abort while the d/l is in progress it becomes a d/l error and not an abort.....why try to con volute the problem by punishing people for wanting equal credit for equal time? Seems the time you would have admin spending doing all this could be time spent actually solving the problem ;)

The last time someone posted that the daily quota was not enough for him GDF raised it almost immediately.. so I really think they're not going to reduce it now.

And they're aware of the credit issue and are trying to correct it, see here. And now that the scheduler issue is finally resolved they have more time to deal with other problems.

And the first post in this thread is actually very valuable, especially if the wall clock time confirms the long run time. They need such feedback to better adjust the credits. However, I wouldn't call it "sucks the big one!" .. compared to the 1888-credit WUs these ones are almost a good fit ;)

MrS

---

Scanning for our furry friends since Jan 2002

damn...
http://www.gpugrid.net/workunit.php?wuid=161268
A 5 hour WU on a GTX260 for 2933 credits- almost twice the 'normal' WU CPU time-WTF??!
And my wingman aborted- rightfully so!
And I noticed one of the uploading files was 12.78MB... I had not noticed any files this big uploading before

damn...
http://www.gpugrid.net/workunit.php?wuid=161268
A 5 hour WU on a GTX260 for 2933 credits- almost twice the 'normal' WU CPU time-WTF??!
And my wingman aborted- rightfully so!
And I noticed one of the uploading files was 12.78MB... I had not noticed any files this big uploading before

I have seen files this big uploaded on a consistent basis. Can't say about the work time though, I don't have any "big" cards:(.

---

mike

damn...
http://www.gpugrid.net/workunit.php?wuid=161268

This WU: 26160 s, 2932 credits -> 404 cr/h
Old WU: 23800 s, 3232 credits -> 489 cr/h
Old WU: 17200 s, 1888 credits -> 395 cr/h

Seems like the new one is based on the same flop estimate as the 1888-credit WUs.

MrS

---

Scanning for our furry friends since Jan 2002