E@H task is not completing

Forums › Problems and Bug Reports

Roelof
Roelof
Joined: 20 Mar 15
Posts: 5
Credit: 102514941
RAC: 41826
9 May 2015 10:54:28 UTC
Topic 198086
(moderation:
    )

    After using BOINC for E@H for a few months now, since the last few days I discover a task that does not make any progress any more (stuck at 98,609%), although its estimated completion time counts down just like the other tasks and eventually show the 'finished' state (3 dashes). I tried to stop and restart the taks, the system acknowledges my actions, but the task still seems is stuck. Anyting else I can try please? Thanks.

    mikey
    mikey
    Joined: 22 Jan 05
    Posts: 12817
    Credit: 1881119390
    RAC: 1138437

    E@H task is not completing

    10 May 2015 10:38:05 UTC
    Message 132417
    (moderation:
      )

      Quote:
      After using BOINC for E@H for a few months now, since the last few days I discover a task that does not make any progress any more (stuck at 98,609%), although its estimated completion time counts down just like the other tasks and eventually show the 'finished' state (3 dashes). I tried to stop and restart the taks, the system acknowledges my actions, but the task still seems is stuck. Anyting else I can try please? Thanks.

      Exit Boinc, restart the pc and see what happens to the unit, I'm guessing it will jump back to a checkpoint and start crunching again from that point forwards. If not just abort it and move on, not all units can be crunched, some are just flawed. Aborting a unit just puts it back into the cache for some other pc to try and crunch.

      Roelof
      Roelof
      Joined: 20 Mar 15
      Posts: 5
      Credit: 102514941
      RAC: 41826

      RE: RE: After using BOINC

      10 May 2015 11:58:16 UTC
      Message 132418 in response to message 132417
      (moderation:
        )

        Quote:
        Quote:
        After using BOINC for E@H for a few months now, since the last few days I discover a task that does not make any progress any more (stuck at 98,609%), although its estimated completion time counts down just like the other tasks and eventually show the 'finished' state (3 dashes).(...)

        Exit Boinc, restart the pc and see what happens to the unit,
        (...)

        Thanks for the reply.

        The stuck task was already there the day before; my attempts to trigger the task were taken the next day, hence after a system restart.

        But...
        In teh meantime, the task miraculously appeared to have finished after quite some time crunching the next day. And I discovered another stuck task later, which appeared to have disappeared also.

        Now I think this type of tasks has a progress flow far different from the others (they had the same name prefix).

        So next time I'll have to be more patient... ;-)

        mikey
        mikey
        Joined: 22 Jan 05
        Posts: 12817
        Credit: 1881119390
        RAC: 1138437

        RE: RE: RE: After using

        11 May 2015 10:45:17 UTC
        Message 132419 in response to message 132418
        (moderation:
          )

          Quote:
          Quote:
          Quote:
          After using BOINC for E@H for a few months now, since the last few days I discover a task that does not make any progress any more (stuck at 98,609%), although its estimated completion time counts down just like the other tasks and eventually show the 'finished' state (3 dashes).(...)

          Exit Boinc, restart the pc and see what happens to the unit,
          (...)

          Thanks for the reply.

          The stuck task was already there the day before; my attempts to trigger the task were taken the next day, hence after a system restart.

          But...
          In teh meantime, the task miraculously appeared to have finished after quite some time crunching the next day. And I discovered another stuck task later, which appeared to have disappeared also.

          Now I think this type of tasks has a progress flow far different from the others (they had the same name prefix).

          So next time I'll have to be more patient... ;-)

          Yes you have some LONG crunching times sometimes, here is a short list of your cpu tasks times: 29,086.37, 29,019.71, 29,172.09, 28,597.88, 29,457.23, 50,837.60, 46,436.72, 56,109.31 etc. The key is they all seem to be validating and your getting credits for them, so yes I too would just persevere thru them.

          I see you are also running gpu tasks too, do you leave a cpu core free just to keep the gpu fed?

          Roelof
          Roelof
          Joined: 20 Mar 15
          Posts: 5
          Credit: 102514941
          RAC: 41826

          RE: Yes you have some LONG

          11 May 2015 12:12:53 UTC
          Message 132420 in response to message 132419
          (moderation:
            )

            Quote:
            Yes you have some LONG crunching times sometimes, here is a short list of your cpu tasks times: 29,086.37, 29,019.71, 29,172.09, 28,597.88, 29,457.23, 50,837.60, 46,436.72, 56,109.31 etc. The key is they all seem to be validating and your getting credits for them, so yes I too would just persevere thru them.

            These times are probably measured between start and finish. This can be quite long, because my computer is powered on during a few hours a day only.

            Quote:
            I see you are also running gpu tasks too, do you leave a cpu core free just to keep the gpu fed?

            I have no idea. Things run as default configured by BOINC. Perhaps I may have enabled the usage of the GPU when I first installed it a few months ago. The only thing I observed is that GPU cruching starts a few minutes after I left the computer idle. Meanwhile all 8 cores are running other tasks. Should I dedicate one core to feed the GPU in my situation where the system is powered on and off quite often? (And sometimes I initiate the project update manually.)

            mikey
            mikey
            Joined: 22 Jan 05
            Posts: 12817
            Credit: 1881119390
            RAC: 1138437

            RE: RE: Yes you have some

            12 May 2015 11:26:41 UTC
            Message 132421 in response to message 132420
            (moderation:
              )

              Quote:
              Quote:
              Yes you have some LONG crunching times sometimes, here is a short list of your cpu tasks times: 29,086.37, 29,019.71, 29,172.09, 28,597.88, 29,457.23, 50,837.60, 46,436.72, 56,109.31 etc. The key is they all seem to be validating and your getting credits for them, so yes I too would just persevere thru them.

              These times are probably measured between start and finish. This can be quite long, because my computer is powered on during a few hours a day only.

              No problem.

              Quote:
              Quote:
              I see you are also running gpu tasks too, do you leave a cpu core free just to keep the gpu fed?

              I have no idea. Things run as default configured by BOINC. Perhaps I may have enabled the usage of the GPU when I first installed it a few months ago. The only thing I observed is that GPU cruching starts a few minutes after I left the computer idle. Meanwhile all 8 cores are running other tasks. Should I dedicate one core to feed the GPU in my situation where the system is powered on and off quite often? (And sometimes I initiate the project update manually.)

              Yes I would write down how long the current gpu units are taking, just use the valid units list from the website, then change it so one cpu core is free, ie only running 7 cpu units at a time, and see what the new time to completion is on your gpu units after 24 hours. Since you have an Nvidia gpu it may not make alot of difference, but it could and that's what you are looking for, doing more work faster.

              Comment viewing options

              Select your preferred way to display the comments and click "Save settings" to activate your changes.

              Forums › Problems and Bug Reports