Advanced search

Message boards : Number crunching : Slower cards, busier computers - Handle WU scheduling manually

Author Message
Scott A. Howard
Send message
Joined: 29 Dec 08
Posts: 9
Credit: 9,407
RAC: 0
Level

Scientific publications
wat
Message 17036 - Posted: 14 May 2010 | 14:34:40 UTC
Last modified: 14 May 2010 | 14:35:47 UTC

There are a number of us with either slower GPUs or busier computers that cannot complete WUs in the 5 day window alloted to them. Here is what I had to resort to, I hope that it helps you set up your strategy if you're in the same boat.

In may case, the computer that I am running GPUGrid on is busy 5 days a week for up to 12 hours. In order to ensure that my WUs don't age out, I do the following.

On Wed morning, I allow the GPUGrid task to get new tasks (Projects tab, Allow new tasks button) and update the project. I get two WUs as a result. I immediately abort one because both will not complete. Then I set the GPUGrid task to No New Tasks so it won't pick up a second one.

The sole WU will now easily complete within the 5 day window because it will get two full days on the weekend. During the Monday and Tuesday slack hours, the GPU will be idle - starting a new job at the beginning of the week may not allow the GPU enough free time to complete on a M-S run. On Wednesday, I repeat the procedure.

Why do I bother with this? Because the 8 cores of my machine are processing other protein projects and the machine is running. It seems like a waste not to put the GPU to work also.

What little tweak from GPUGrid would help? Expand the window to 7 days - we would always see Saturday and Sunday in the processing of these long WUs. Of course, GPUGrid only downloading as many WUs as GPUs you're devoting to the project at a time would mean no manual intervention on my/our part.

Hope that reduces some of the shared frustration in not being able to participate in GPUGrid.

Profile skgiven
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 23 Apr 09
Posts: 3968
Credit: 1,995,359,260
RAC: 0
Level
His
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 17037 - Posted: 14 May 2010 | 14:58:31 UTC - in response to Message 17036.

If you set your cache to 0.05 days before asking for GPU work you would only download 1 GPU task and you would not have to abort the other!

GPUGrid tasks depend on the previous results, so if you have to wait 2 extra days between each batch, then that would slow the project down by about 40% each round, and like the banks its compound.

I think there are ways to include older cards:
To specifically identify them and make separate smaller tasks for them,
have them predominately run smaller Betas and Test work,
have them run on completely different projects.

However, such suggestions are easier said than done.

Betting Slip
Send message
Joined: 5 Jan 09
Posts: 670
Credit: 2,498,095,550
RAC: 0
Level
Phe
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 17040 - Posted: 14 May 2010 | 15:15:36 UTC - in response to Message 17036.
Last modified: 14 May 2010 | 15:16:42 UTC



The sole WU will now easily complete within the 5 day window because it will get two full days on the weekend.



I'm afraid your strategy is flawed and a waste of your time and GPU because while the project gives you 5 days to return the WU and get credit, it will resend the WU to a fast host if you reach and breach 2 days and that host will more than likely return in less than 24hrs thus beating your host by at least 2 days. You'll still get basic credit but in this scenario your result as far as the project is concerned will be discarded.

Skgiven, explains why in his post above.
____________
Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Scott A. Howard
Send message
Joined: 29 Dec 08
Posts: 9
Credit: 9,407
RAC: 0
Level

Scientific publications
wat
Message 17041 - Posted: 14 May 2010 | 15:34:37 UTC - in response to Message 17040.

OK, it's a total waste of time.

The question is then, why in the world would you give credit when the results are discarded? Just how much credit is being awarded for results that you discard? Why don't you notify those processing discarded WUs that they are discarded?

Wouldn't the project be more transparent and honest if you simply didn't award the credit? You have the benchmark results for each system. Why in the world don't you put a lower bounds on the metrics and deny WUs to those systems?

It really appears that the whole GPUGrid project has issues. It's apparent that the group does not have experience in product management and requirements management. You are also not working well with the community based on the repeated threads on the same issues.

You probably don't understand these issues right now. When you guys get out of school and deal with real world projects, you'll look back and see how poorly you are managing the external aspects of your project.

Good luck with the project and results. As a former practicing crystallographer, I appreciate the work in protein structures and believe that, among all the BOIN projects, these are the most rewarding.

<disconnect>

bigtuna
Volunteer moderator
Send message
Joined: 6 May 10
Posts: 80
Credit: 98,784,188
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwat
Message 17190 - Posted: 20 May 2010 | 22:21:09 UTC - in response to Message 17041.

OK, it's a total waste of time.

The question is then, why in the world would you give credit when the results are discarded? Just how much credit is being awarded for results that you discard? Why don't you notify those processing discarded WUs that they are discarded?

To give you credit for your effort, I presume.



It really appears that the whole GPUGrid project has issues. It's apparent that the group does not have experience in product management and requirements management. You are also not working well with the community based on the repeated threads on the same issues.

You probably don't understand these issues right now. When you guys get out of school and deal with real world projects, you'll look back and see how poorly you are managing the external aspects of your project.

Good luck with the project and results. As a former practicing crystallographer, I appreciate the work in protein structures and believe that, among all the BOIN projects, these are the most rewarding.

<disconnect>

I suspect that the folks at the GRID are doing the best they can. If you really want to help, why not just pick up a GT240 for $40 to $60 (after rebate)? A GT240 will return a typical work unit in 10-12 hours which seems perfect for your situation.


Post to thread

Message boards : Number crunching : Slower cards, busier computers - Handle WU scheduling manually

//