Too much work
12 May 2005 2:27:21 UTC
Topic 189166
(moderation:
I am using BOINC 4.32 on a Pentium II with SuSE Linux 9.1. As soon as I start a WU I get a new one which sits idle while the first is computed, consuming allotted time before its deadline, so I am always late. With BOINC 4.19 I used to receive a new WU just before the previous ended and there was little overlapping between the WU being processed and the one in wait. What cam I do?
Too much work
)
I am using BOINC 4.32 on a Pentium II with SuSE Linux 9.1. As soon as I start a WU I get a new one which sits idle while the first is computed, consuming allotted time before its deadline, so I am always late. With BOINC 4.19 I used to receive a new WU just before the previous ended and there was little overlapping between the WU being processed and the one in wait. What cam I do?
Go to Boinc 4.25 . I had this behavior with 4.35, 4.37 and 4.38 also. Regardless of how small my connect time was. I tried .1, .01 and .001 and it still would download a new WU as soon as it started one.
Boinc 4.25 follows your connection preferences. :-)
I am using BOINC 4.32 on a
)
I am using BOINC 4.32 on a Pentium II with SuSE Linux 9.1. As soon as I start a WU I get a new one which sits idle while the first is computed, consuming allotted time before its deadline, so I am always late. With BOINC 4.19 I used to receive a new WU just before the previous ended and there was little overlapping between the WU being processed and the one in wait. What cam I do?
There are many changes to scheduling happening in the 4.3x bleeding edge versions. I notice windoze is already up to 4.38 (with manual updating now broken) whilst linux is still at 4.32. I'd probably be going back to 4.19 and waiting for the dust to settle if I were you :). What happens if you set your "connect" interval to something really low like 0.02 which should mean about 30 mins of cpu time left for completion?
Cheers,
Gary.
I would have edited my post
)
I would have edited my post but something is wrong with the edit function.
I just saw on the Boinc software download page that 4.25 isn't listed for Linux, just 4.19 and 4.32 - I don't know if there were some problems with 4.25 on Linux machines.
Sorry about that.
Go to Boinc 4.25 . I had this
)
Go to Boinc 4.25 . I had this behavior with 4.35, 4.37 and 4.38 also. Regardless of how small my connect time was. I tried .1, .01 and .001 and it still would download a new WU as soon as it started one.
Boinc 4.25 follows your connection preferences. :-)
There doesn't seem to be a 4.25 for linux - only 4.19 and 4.32 are listed. Did you try .1, .01, .001, with a linux system or are you talking about windoze?
Cheers,
Gary.
I am using BOINC 4.32 on a
)
I am using BOINC 4.32 on a Pentium II with SuSE Linux 9.1. As soon as I start a WU I get a new one which sits idle while the first is computed, consuming allotted time before its deadline, so I am always late. With BOINC 4.19 I used to receive a new WU just before the previous ended and there was little overlapping between the WU being processed and the one in wait. What cam I do?
There are many changes to scheduling happening in the 4.3x bleeding edge versions. I notice windoze is already up to 4.38 (with manual updating now broken) whilst linux is still at 4.32. I'd probably be going back to 4.19 and waiting for the dust to settle if I were you :). What happens if you set your "connect" interval to something really low like 0.02 which should mean about 30 mins of cpu time left for completion?
Thanks four your suggestions. I have set the "connect" interval at 0.01 and will see what happens. I like BOINC 4.32 because of its boincmgr GUI. Regards.
I am using BOINC 4.32 on a
)
I am using BOINC 4.32 on a Pentium II with SuSE Linux 9.1. As soon as I start a WU I get a new one which sits idle while the first is computed, consuming allotted time before its deadline, so I am always late. With BOINC 4.19 I used to receive a new WU just before the previous ended and there was little overlapping between the WU being processed and the one in wait. What cam I do?
There are many changes to scheduling happening in the 4.3x bleeding edge versions. I notice windoze is already up to 4.38 (with manual updating now broken) whilst linux is still at 4.32. I'd probably be going back to 4.19 and waiting for the dust to settle if I were you :). What happens if you set your "connect" interval to something really low like 0.02 which should mean about 30 mins of cpu time left for completion?
Thanks four your suggestions. I have set the "connect" interval at 0.01 and will see what happens. I like BOINC 4.32 because of its boincmgr GUI. Regards.
No way. I am still getting another WU as soon as one is finished and the one in wait has just started. But as long as they are accepted I don't care. This is called pipelining in microprocessor jargon. But my poor old Pentium II at 400 MHz is not exactly a pipelining champion.
I am using BOINC 4.32 on a
)
I am using BOINC 4.32 on a Pentium II with SuSE Linux 9.1. As soon as I start a WU I get a new one which sits idle while the first is computed, consuming allotted time before its deadline, so I am always late. With BOINC 4.19 I used to receive a new WU just before the previous ended and there was little overlapping between the WU being processed and the one in wait. What cam I do?
There are many changes to scheduling happening in the 4.3x bleeding edge versions. I notice windoze is already up to 4.38 (with manual updating now broken) whilst linux is still at 4.32. I'd probably be going back to 4.19 and waiting for the dust to settle if I were you :). What happens if you set your "connect" interval to something really low like 0.02 which should mean about 30 mins of cpu time left for completion?
Thanks four your suggestions. I have set the "connect" interval at 0.01 and will see what happens. I like BOINC 4.32 because of its boincmgr GUI. Regards.
No way. I am still getting another WU as soon as one is finished and the one in wait has just started. But as long as they are accepted I don't care. This is called pipelining in microprocessor jargon. But my poor old Pentium II at 400 MHz is not exactly a pipelining champion.
Looks like I have broken the vicious loop. I have one WU running late but the next one should be able to start as soon as it is downloaded and so have its allotted time in full.