Message boards :
Number crunching :
FUBAR!
Message board moderation
Author | Message |
---|---|
Send message Joined: 19 Aug 11 Posts: 76 Credit: 2,002,860 RAC: 0 |
i only want to run Get Bounded Decics. i am not getting a single WU for days now. should i stay or should i go? |
Send message Joined: 8 Jul 11 Posts: 46 Credit: 7,144,042 RAC: 0 |
i only want to run Get Bounded Decics. Sorry about that. I think the weights were messed up again and confusing the server with fractional values. I just changed them to something that looks reasonable. It should be possible to just run the Get Bounded Decics app if you want to. |
Send message Joined: 8 Jul 11 Posts: 1323 Credit: 410,726,866 RAC: 245,383 |
Sorry, I have been in meetings all day. I don't think the fractional values are what messed up the server. I think the problem is that the equivalent ratio was something like 100 to 1 (in favor of the GetDecics app). I could be wrong here, but I think the server keeps an internal queue of the WUs it's going to distribute; when the ratio is 100 to 1, GetBoundedDecics ends up with very few WUs in the queue, if any. For some reason, when I set the ratio to something more reasonable like 3 to 1, it ends up distributing many more WUs for the Bounded app. Maybe there's a lot more people than I thought that are selecting the GetBoundedDecics app in their preferences. So Greg fixed the weights, but let us know if you still can't get work, because we might need to restart the project daemons. May I ask, why you prefer the GetBoundedDecics app? Is it the shorter run times? Because hourly credit is the same for both. I understand if you don't like waiting days to finish a WU, which takes even longer with an older (and slower) CPU. Once the current batch of GetDecic WUs is complete (which may take a couple months at the rate it's going), runtimes should get back to normal. Eric |
Send message Joined: 19 Aug 11 Posts: 76 Credit: 2,002,860 RAC: 0 |
May I ask, why you prefer the GetBoundedDecics app? Is it the shorter run times? exactly. Because hourly credit is the same for both. I understand if you don't like waiting days to finish a WU, which takes even longer with an older (and slower) CPU. that's not the problem. i am currently running most of them on a laptop which has only a few hours of spare time for boinc. |
Send message Joined: 2 Sep 11 Posts: 57 Credit: 1,274,345 RAC: 0 |
that's not the problem. i am currently running most of them on a laptop which has only a few hours of spare time for boinc. That's one of the reasons the deadline (not the grace period but the actual deadline because THAT, not the grace period, is all 99% of people see) needs to be increased. Add the confusion and uncertainty the scheduler throws into the mix and you end up with a lot of people who won't crunch tasks that run longer than 24 hours. Lots of people reason that the longer a task runs the more chance it has of crashing and not receiving credit so they don't like long tasks to begin with. Add another straw (short deadlines) and the camel quits. Again, a long grace period is irrelevant as 99% of people have no idea a grace period exists or, if they do know, they have no idea how long the period is. Why don't they ask? It's easier to just click No New Tasks, detach the project or select only the short tasks. There are some things people just will not do no matter how many worthless credits you give them so you best remove as many impediments as possible. Do you really need results back that quickly? Some project admins admit that short deadlines are no help and that it's all driven by resource share and numbers of volunteers. That makes sense. If you double the deadline you'll wait twice as long for the first result to return but once the ball gets rolling the results come back just as quickly as with a short deadline because it's all driven by resource share and number of volunteers. A short deadline does not mean a result returns sooner, it means the host will wait longer before downloading a task. If a host's resource share allows for 1 of your tasks per week than you'll get 1 result per week regardless of what the deadline is though if it's too short for the user's liking he'll just boot your project to the curb. The tortoise versus the hare. BOINC FAQ Service Official BOINC wiki Installing BOINC on Linux |
Send message Joined: 19 Aug 11 Posts: 76 Credit: 2,002,860 RAC: 0 |
and again, the silly sheduler shows work is available, but it refuses to hand them out: 09.03.2012 15:58:20 | NumberFields@home | Sending scheduler request: To fetch work. 09.03.2012 15:58:20 | NumberFields@home | Requesting new tasks for CPU 09.03.2012 15:58:22 | NumberFields@home | Scheduler request completed: got 0 new tasks 09.03.2012 15:58:22 | NumberFields@home | No tasks sent 09.03.2012 15:58:22 | NumberFields@home | No tasks are available for Get Decics with Bounded Discriminant well, then another project will profit.. |
Send message Joined: 8 Jul 11 Posts: 1323 Credit: 410,726,866 RAC: 245,383 |
Not sure why it's doing that this time. I restarted the project just for good measure. Please let me know if it continues to behave this way, so I can look into this further. |
Send message Joined: 28 Oct 11 Posts: 179 Credit: 223,759,430 RAC: 112,756 |
If you double the deadline you'll wait twice as long for the first result to return but once the ball gets rolling the results come back just as quickly .... Agree totally about the flow rate, but a long pipeline increases the number of tasks in flight. Fot some projects, that has a significant impact on the server specification - storage size requirement for both the database and workunit data files. But the data files here won't be a major problem... |
Send message Joined: 19 Aug 11 Posts: 76 Credit: 2,002,860 RAC: 0 |
If you double the deadline you'll wait twice as long for the first result to return but once the ball gets rolling the results come back just as quickly .... nope - 4 weeks deadline for getdecis should be fine and be nice even for part time crunchers. |
Send message Joined: 19 Aug 11 Posts: 76 Credit: 2,002,860 RAC: 0 |
Not sure why it's doing that this time. I restarted the project just for good measure. Please let me know if it continues to behave this way, so I can look into this further. works - for now.. |