Message boards : Number crunching : New WU -- no check point.
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Aurora Borealis

Send message
Joined: 18 Sep 04
Posts: 59
Credit: 317,857
RAC: 0
Message 6891 - Posted: 9 Apr 2005, 4:36:54 UTC

I got a couple of v64boince WU a few hours ago.
I checked my message log and have been working on
v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
It has been paused twice and apparently it has a similar problem to the old LHC WU. It reset to 0% and 0 CPU time when it is restarted.


Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB
ID: 6891 · Report as offensive     Reply Quote
Profile littleBouncer
Avatar

Send message
Joined: 23 Oct 04
Posts: 358
Credit: 1,439,205
RAC: 0
Message 6896 - Posted: 9 Apr 2005, 6:34:57 UTC - in response to Message 6891.  
Last modified: 9 Apr 2005, 6:48:31 UTC

> I got a couple of v64boince WU a few hours ago.
> I checked my message log and have been working on
> v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> It has been paused twice and apparently it has a similar problem to the old
> LHC WU. It reset to 0% and 0 CPU time when it is restarted.
>
>
>
@ Aurora Borealis
From which WU do you talk about? Please copy/paste the WU ID or the Link.
And 4.64 are 'old' WU's; the 'new ones' call: 4.66.

I didn't see any in your resultstable from today an yesterday (8/9.April)!
(you didn't report it yet)

greetz littleBouncer

ID: 6896 · Report as offensive     Reply Quote
Aurora Borealis

Send message
Joined: 18 Sep 04
Posts: 59
Credit: 317,857
RAC: 0
Message 6904 - Posted: 9 Apr 2005, 11:11:15 UTC - in response to Message 6896.  


> From which WU do you talk about? Please copy/paste the WU ID or the Link.
> And 4.64 are 'old' WU's; the 'new ones' call: 4.66.
>
> I didn't see any in your resultstable from today an yesterday (8/9.April)!
> (you didn't report it yet)
>
> greetz littleBouncer
>
It's hard to report a WU that keeps resetting at O% processed. I now need to suspend all my other projects to allow this one to be completed. I will be doing so now and will post again, in four to six hr, when I have completed a WU.

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB
ID: 6904 · Report as offensive     Reply Quote
STE\/E

Send message
Joined: 2 Sep 04
Posts: 352
Credit: 1,393,150
RAC: 0
Message 6905 - Posted: 9 Apr 2005, 11:24:19 UTC
Last modified: 9 Apr 2005, 11:26:37 UTC

I just reported 2 WU's that took about 11 hours each and they showed 0:00:00 Time, they were the 4.64 applications ... Here's one of WU's ... I'm host 30594 ... I've had numerous other ones with the 4.64 application show 0:00:00 time also on my other Computers ...
ID: 6905 · Report as offensive     Reply Quote
Kenneth Larsen

Send message
Joined: 2 Sep 04
Posts: 36
Credit: 90,806
RAC: 0
Message 6908 - Posted: 9 Apr 2005, 11:55:53 UTC
Last modified: 9 Apr 2005, 11:58:47 UTC

I have one as well, this one. It has been crunching all night and has reset a couple of times, starting from scratch. I hope to have it finished in a few hours though (crossing fingers ;-)).
ID: 6908 · Report as offensive     Reply Quote
Holmis

Send message
Joined: 17 Sep 04
Posts: 10
Credit: 5,620
RAC: 0
Message 6909 - Posted: 9 Apr 2005, 12:47:35 UTC
Last modified: 9 Apr 2005, 12:49:16 UTC

My first WU with the new app 4.66 seems to checkpoint ok.
I shutdown boinc to defrag my harddrive and when I restarted it continued from the 10% it reached before the shutdown. All seems fine so far.

This is the WU
I'm host 21859.
ID: 6909 · Report as offensive     Reply Quote
Kenneth Larsen

Send message
Joined: 2 Sep 04
Posts: 36
Credit: 90,806
RAC: 0
Message 6916 - Posted: 9 Apr 2005, 15:58:47 UTC

No, I can't finish any LHC units on this computer, since it constantly restarts due to faulty hardware (I think). I've been through 4 wus now that resume at 0%. Any chance this will get fixed? I now it worked before.
ID: 6916 · Report as offensive     Reply Quote
Aurora Borealis

Send message
Joined: 18 Sep 04
Posts: 59
Credit: 317,857
RAC: 0
Message 6918 - Posted: 9 Apr 2005, 18:55:18 UTC
Last modified: 9 Apr 2005, 19:04:27 UTC

After several hours of processing,
v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
I had to reboot my computer, and reluctantly decided to abort it.
The second WU
v64boince6ib1-25s14_16615_1_sixvf_1069_0 using sixtrack version 4.64
completed successfully in only a few minutes.
I am now processing
v64boince6ib1b-37s14_16630_1_sixvf_28681_1 using sixtrack version 4.66
it seems to pauses and restarts properly.

edit:: The above just completed. I had just checked it and it was at 15% a few seconds later it was finished. Successfully !!! I have my doubts.
Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB
ID: 6918 · Report as offensive     Reply Quote
Profile littleBouncer
Avatar

Send message
Joined: 23 Oct 04
Posts: 358
Credit: 1,439,205
RAC: 0
Message 6919 - Posted: 9 Apr 2005, 19:36:16 UTC - in response to Message 6918.  

> After several hours of processing,
> v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> I had to reboot my computer, and reluctantly decided to abort it.
-----
For this : I have no explain yet. There is a lot to tell about, but as 4.64 will be gone soon, it isn't worth to open a new 'construction site'...

> The second WU
> v64boince6ib1-25s14_16615_1_sixvf_1069_0 using sixtrack version 4.64
> completed successfully in only a few minutes.
> I am now processing
> v64boince6ib1b-37s14_16630_1_sixvf_28681_1 using sixtrack version 4.66
> it seems to pauses and restarts properly.
-----
This two WU's are 's14_' and will take 10 min. (average) or about 1.38889% of the time which a 's6_' will take.
So for me the behaviour was 'normal' .

>
> edit:: The above just completed. I had just checked it and it was at 15% a few
> seconds later it was finished. Successfully !!! I have my doubts.
>
-----
Don't doubt! It will work, let your client play....;-)
greetz littleBouncer

ID: 6919 · Report as offensive     Reply Quote
bass4lhc

Send message
Joined: 28 Sep 04
Posts: 43
Credit: 249,962
RAC: 0
Message 6924 - Posted: 9 Apr 2005, 22:58:22 UTC - in response to Message 6891.  

> I got a couple of v64boince WU a few hours ago.
> I checked my message log and have been working on
> v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> It has been paused twice and apparently it has a similar problem to the old
> LHC WU. It reset to 0% and 0 CPU time when it is restarted.
>
i have the same problem on at least 4 computers.
all intel/winxp/sixtrack4.64
after every switch between projects the lhc@home wu's restart at 0%.
this way i never get any work done and lhc@home is wasting my donated time.

resetting these computers makes no difference.
i am not going to stop the other projects i am donating too, to resolve this problem.

can i just delete the lhc wu's and hope to get wu's that do work?
ID: 6924 · Report as offensive     Reply Quote
Aurora Borealis

Send message
Joined: 18 Sep 04
Posts: 59
Credit: 317,857
RAC: 0
Message 6925 - Posted: 9 Apr 2005, 23:38:39 UTC - in response to Message 6924.  
Last modified: 9 Apr 2005, 23:40:08 UTC

> > I got a couple of v64boince WU a few hours ago.
> > I checked my message log and have been working on
> > v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> > It has been paused twice and apparently it has a similar problem to the
> old
> > LHC WU. It reset to 0% and 0 CPU time when it is restarted.
> >
> i have the same problem on at least 4 computers.
> all intel/winxp/sixtrack4.64
> after every switch between projects the lhc@home wu's restart at 0%.
> this way i never get any work done and lhc@home is wasting my donated time.
>
> resetting these computers makes no difference.
> i am not going to stop the other projects i am donating too, to resolve this
> problem.
>
> can i just delete the LHC wu's and hope to get wu's that do work?

If you use Boinc V4.2x you can abort individual WU by highlighting them in the Work tab and selecting Abort result in the tasks window. Other than that you could detach from the project, that would kill all the WU.
I am not sure what file you need to delete to make WU error out.

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB
ID: 6925 · Report as offensive     Reply Quote
bass4lhc

Send message
Joined: 28 Sep 04
Posts: 43
Credit: 249,962
RAC: 0
Message 6926 - Posted: 10 Apr 2005, 0:11:23 UTC - in response to Message 6925.  
Last modified: 10 Apr 2005, 1:03:55 UTC

> If you use Boinc V4.2x you can abort individual WU by highlighting them in the
> Work tab and selecting Abort result in the tasks window. Other than that you
> could detach from the project, that would kill all the WU.
> I am not sure what file you need to delete to make WU error out.
>
@ aurora borealis: thank you for your answer. i did not know there was a new boinc version.
maybe the boinc people could find a way to let us know???

i will try your solution.

i see in the lhc download section only version 4.19, which i was using.
i am now running boinc 4.25. let's see what happens now.....

and some time later i see the problem still is there.
as usual there is no info from lhc. so i am going to abort results.

ID: 6926 · Report as offensive     Reply Quote
Profile Ed and Harriet Griffith
Avatar

Send message
Joined: 18 Sep 04
Posts: 37
Credit: 4,051
RAC: 0
Message 6929 - Posted: 10 Apr 2005, 2:47:20 UTC

I have processed a few of the new work units and they vary in time from 2 to 35 minutes.

ID: 6929 · Report as offensive     Reply Quote
Aurora Borealis

Send message
Joined: 18 Sep 04
Posts: 59
Credit: 317,857
RAC: 0
Message 6931 - Posted: 10 Apr 2005, 3:45:04 UTC - in response to Message 6929.  

> I have processed a few of the new work units and they vary in time from 2 to
> 35 minutes.
>
Different WU have various processing time.
The S## is your clue. The smaller number seem to take longer.
e.g.
v64boince6ib1b-37s14 was only 17 min
v64boince6ib1b-38s12 was 1 hr
currently processing
v64boince6ib1b-41s8 already over 3hr

Boinc V4.27 alpha
Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB
ID: 6931 · Report as offensive     Reply Quote
Kenneth Larsen

Send message
Joined: 2 Sep 04
Posts: 36
Credit: 90,806
RAC: 0
Message 6934 - Posted: 10 Apr 2005, 10:27:12 UTC

I just discovered this: If you let units stay in memory when suspended, they won't restart after having been suspended. Strangely enough, they also continue after the machine has been restarted.
The setting is found under "Your Account" -> "General Preferences" -> "Leave applications in memory while preempted?".

Hope this helps you, it certainly helped me.
ID: 6934 · Report as offensive     Reply Quote
Profile littleBouncer
Avatar

Send message
Joined: 23 Oct 04
Posts: 358
Credit: 1,439,205
RAC: 0
Message 6935 - Posted: 10 Apr 2005, 10:36:27 UTC - in response to Message 6934.  
Last modified: 10 Apr 2005, 10:37:03 UTC

> I just discovered this: If you let units stay in memory when suspended, they
> won't restart after having been suspended. Strangely enough, they also
> continue after the machine has been restarted.
> The setting is found under "Your Account" -> "General Preferences" ->
> "Leave applications in memory while preempted?".
>
> Hope this helps you, it certainly helped me.
-----
It helps!

I forgot to suggest it, sorry
greetz littleBouncer
ID: 6935 · Report as offensive     Reply Quote
Vid Vidmar*
Avatar

Send message
Joined: 28 Sep 04
Posts: 27
Credit: 17,091
RAC: 0
Message 6936 - Posted: 10 Apr 2005, 11:09:00 UTC - in response to Message 6934.  

> I just discovered this: If you let units stay in memory when suspended, they
> won't restart after having been suspended. Strangely enough, they also
> continue after the machine has been restarted.
> The setting is found under "Your Account" -> "General Preferences" ->
> "Leave applications in memory while preempted?".
>
> Hope this helps you, it certainly helped me.

Now I understand why I didn't have this problem. I turned this setting on, when I read somwhere, that CPDN backs 170TS on restart if app. isn't preempted.

Happy crunching,

ID: 6936 · Report as offensive     Reply Quote
[SFX] gD

Send message
Joined: 23 Oct 04
Posts: 8
Credit: 28,043
RAC: 0
Message 6941 - Posted: 10 Apr 2005, 12:49:34 UTC - in response to Message 6936.  

> when I read somwhere, that CPDN backs 170TS on restart if app. isn't

Actually, UP TO 144 TS.

Has anyone bothered to find out how often a checkpoint is in LHC WUs? (or has admin said it somewhere?)

Also if Aurora Borealis kept having the entire WU reset to 0, might there be a long time between each checkpoint or are his BOINC timeslices really short?

ID: 6941 · Report as offensive     Reply Quote
Aurora Borealis

Send message
Joined: 18 Sep 04
Posts: 59
Credit: 317,857
RAC: 0
Message 6942 - Posted: 10 Apr 2005, 12:53:27 UTC - in response to Message 6934.  
Last modified: 10 Apr 2005, 13:00:00 UTC

> I just discovered this: If you let units stay in memory when suspended, they
> won't restart after having been suspended. Strangely enough, they also
> continue after the machine has been restarted.
> The setting is found under "Your Account" -> "General Preferences" ->
> "Leave applications in memory while preempted?".
>
> Hope this helps you, it certainly helped me.
>
I forgot to mention this.... because it causes other problems with Windows 98.
You end up with several projects apparently running at the same time, and getting very long crunch time to nowhere. I think youre OK with other OS.

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB
ID: 6942 · Report as offensive     Reply Quote
Profile Chrulle

Send message
Joined: 27 Jul 04
Posts: 182
Credit: 1,880
RAC: 0
Message 6944 - Posted: 10 Apr 2005, 14:22:45 UTC

When we checkpoint depends on the specific study and sixtrack version, but i believe it is about every 1000 turns.

BUT!!! We only checkpoint if the boinc_time_to_checkpoint() function returns true.
This function is there to limit how often we write to disk, so that people on laptops, for example, can save power.

How often we can checkpoint is therefore something that you can limit in your preferences.

Chrulle
Research Assistant & Ex-LHC@home developer
Niels Bohr Institute
ID: 6944 · Report as offensive     Reply Quote
1 · 2 · Next

Message boards : Number crunching : New WU -- no check point.


©2024 CERN