I hate those guys :-) |
![]() |
| log in |
Message boards : Number crunching : I hate those guys :-)
| Author | Message |
|---|---|
|
I have 23 AP tasks pending, and all my wingman's stop their computers for so long. | |
| ID: 1131632 · | |
Then you'll have to wait a bit longer. :) ____________ Goodbye Seti Classic | |
| ID: 1131743 · | |
Better Yet, Buy your wingman or woman an I7 980 :) ____________ | |
| ID: 1131749 · | |
or even better, fed-ex it to me & I'll become your permanent wingman...lol ____________ | |
| ID: 1131751 · | |
|
Just wondering, can you be your own wingman if you have more than one computer? | |
| ID: 1131757 · | |
Just wondering, can you be your own wingman if you have more than one computer? I suspect so, although I can't say that I have seen anybody post such an occurrence. I think the scheduler doles work out keeping track of individual hosts without concern for the master account they are attached to. So I don't see why it could not happen. As to the odds....... ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1131763 · | |
Just wondering, can you be your own wingman if you have more than one computer? Yeah, both of your machines would have to hit the scheduler at pretty much the exact same time... Tough to do even with simultaneous manual update requests. ____________ Donald Infernal Optimist / Submariner, retired | |
| ID: 1131804 · | |
Just wondering, can you be your own wingman if you have more than one computer? This project uses the project configuration setting <one_result_per_user_per_wu/>, so one account should never get two tasks for the same WU. Without that or the similar <one_result_per_host_per_wu/> a single work request would often get both of the tasks for a single WU because the initial replication puts the two tasks adjacent in the "Results ready to send" queue. Joe | |
| ID: 1131835 · | |
I have 23 AP tasks pending, and all my wingman's stop their computers for so long. It's called Volunteer Computing and dedication varies -- a lot. If you want to eliminate things like late (or lost) work, you simply have to limit the project to the most reliable volunteers and most reliable computers. Once you do that (and eliminate the vast majority of the volunteers) then these sorts of events will be quite rare. But that's not reality. We should be saying "look how well all this stuff works with random hardware and casual volunteers!" Waiting is. | |
| ID: 1131838 · | |
|
Guess we know who's not in it for the science lol. | |
| ID: 1132113 · | |
Message boards : Number crunching : I hate those guys :-)
| Copyright © 2013 University of California |