Posts by unnefer

1) Message boards : News : bypassing server set cache limits (Message 46842) Posted 30 Mar 2011 by unnefer Post: If people have large caches, that means the work they're crunching can come from very old versions of those populations which have since evolved quite a bit away from where they were when the user filled up their cache. When they return the results there's a lower chance for the results to improve the population of results we're currently working with. <br> So that's why our cache is so low --Travis Travis, This is not exactly true and I'm sure you know it. Ppl using faster GPUs will crunch more workunits in the same time as a person with a slower GPU. For example, a person with a 5870 can crunch a wu twice as quick as a person with a 4870, yet they get the same amount of maximum taks. Going by your comment, this in itself would also be a bad thing, because the 5870 will finish all 6 tasks before the 4870 has finished 3 of them, it will then request another 6 tasks and complete those before the 4870 has finished its fist 6 tasks. So the 5870 is going to crunching "newer" versions of those populations and the 4870 will be crunching "older" versions of the populations and in effect they will be contributing to the exact thing you do not want to ocurr. You (mw@h) can penalise the faster gpus as much as you like, but regardless of the wu limit, at any given point in time the faster gpus will be on the "newer" populations while the slower card is still crunching "older" populations. Rather then penalise the faster gpus, you (mw@h) needs to penalise the slower gpus, by either reducing the maximum tasks allowed for the slower gpus or increasing the maximum tasks allowed for the faster gpus. That way, both the slower and the faster cards are always crunching the same "aged" populations. Ideally, you (mw@h) should determine the maximum amount of tasks based on the actual gpu series being used, and then adjust the maximum tasks allowed based on the relative performance between the gpu series. Lastly, I understand that your server may not be able to validate more then 500K workunits per day, but you (mw@h) also need to understand that it is actually costs us us members quite a bit of money (in electricity) to crunch those workunits for you (mw@h). And those of us who actually need a higher task limit do not appreciate having our rigs sit their doing nothing because our BOINC rigs have run out of workunits to process - to have them sit their doing nothing still costing us money. Food for thought.
2) Message boards : News : issue with not getting work resolved (Message 42067) Posted 12 Sep 2010 by unnefer Post: Sorry to dig up an old thread, but this is happening to me right now as well? In my log, it just keeps repeating this: 12/09/2010 10:50:04 PM Milkyway@home Message from server: No work sent 12/09/2010 10:51:09 PM Milkyway@home Sending scheduler request: To fetch work. 12/09/2010 10:51:09 PM Milkyway@home Requesting new tasks for GPU 12/09/2010 10:51:12 PM Milkyway@home Scheduler request completed: got 0 new tasks 12/09/2010 10:51:12 PM Milkyway@home Message from server: No work sent 12/09/2010 10:53:17 PM Milkyway@home Sending scheduler request: To fetch work. 12/09/2010 10:53:17 PM Milkyway@home Requesting new tasks for GPU 12/09/2010 10:53:19 PM Milkyway@home Scheduler request completed: got 0 new tasks 12/09/2010 10:53:19 PM Milkyway@home Message from server: No work sent And never gets any new tasks? Before this, everything worked great, but as of approx 2 hours ago, it just stopped updating. For reference, my userID is 122698 - just in case an admin or whoever is reading and might be able to help.