WU 1599 "abc_wu_19330000_20000" is still at 5,6 % progress after more than 1 hour processing time. How long should I keep it running, if the progress doesn't change ?
/ 
more than 2 hours now and no further progress..
/ 
Yes I have one too : abc_wu_12650000_20000_0
3hrs 30mins in and over 3 hrs to go?
AMD3200XP with Kubuntu v606.
I'll give it another 15 mins or so then kill it and try the next one.
/ 
Hmmm. Yesterday my WU's progress bars also "jumped" sort of.
I remember I had one at 22% for quite a long time. And a team mate had a WU which seemed stuck at 5.9%, too. Her WU finished finally after 11 hours.
I hope you didn't catch such a long one. But I would let it crunch.
Unless our admin says something different at least. ;-)
____________
Lovely greetings from Cori 
/ Please don't abort them, the progress can be really off sometimes.
If you abort it, it will stick in the cache and someone else will get it.
They really need to be worked off sometime, and the credits you get are
the same as if you'd do multiple smaller ones.
EDIT: We don't have run away workunits that never finish, some can just take a while. Aborting is really wasting it.
/ Hendrik - Ok - I'll let it run through for about 8 hours then see what happens.
Thanks for the reply.
/ No problem. I will try to keep an eye on the progress myself now too,
with previous application versions it was pretty accurate, also jumpy sometimes,
but from what I hear now with the new 10^18 maybe we need to re-evaluate it.
Or just get further and further away from the first workunits.
/ WU 1599 finished after 3,5 hours correctly.
/ Long Work Unit finished in 5hrs 20mins - validated OK - credited OK.
/ My first 'long' workunit (ID = 1688) took 3 hrs. 50 sec. on a 2 GHz Athlon64. On the same system the two shortest workunits took only between five and seven minutes (ID = 600, ID = 1330). So, yes, quite some differences.
I also noticed that progress sometimes won't change for some time, seems to happen mostly (?) when calculations have just begun. On my slowest box the workunit (ID = 47) was stuck at 1.4 % for about the first 3 hrs. and I thought it will never make it in time, but then progress increased and the result was finished after ~ 12 hrs. However, hope I never catch a 'long one' on this box...
Regards
Alex
____________
/ My first 'long' workunit (ID = 1688) took 3 hrs. 50 sec. on a 2 GHz Athlon64. On the same system the two shortest workunits took only between five and seven minutes (ID = 600, ID = 1330). So, yes, quite some differences.
I also noticed that progress sometimes won't change for some time, seems to happen mostly (?) when calculations have just begun. On my slowest box the workunit (ID = 47) was stuck at 1.4 % for about the first 3 hrs. and I thought it will never make it in time, but then progress increased and the result was finished after ~ 12 hrs. However, hope I never catch a 'long one' on this box...
Regards
Alex
Same here. I know it's very annoying, for us too.
Let's hope this is settled soon and the workunits are going to behave normally.
In theory, the further we come the better it becomes, it only lasts a bit
longer than anticipated.
/ 
Sit back and listen to some classical music while waiting for those long WUs -
Jimi Hendri(k)
/ Sit back and listen to some classical music while waiting for those long WUs -
Yeah, love that classical piece.
Btw, he played it the same year I was born...
/ Btw, he played it the same year I was born...
.....and I was a mere teenager of 15 years old! That was the last time he played in the UK. He passed on later in that year so I never did get to see the great man perform on stage.....
Here's another one.
(Trivia note - The drum kit is manufactured by a company here in my home-town of Leicester, UK.
http://www.premier-percussion.co.uk/)
/ This WU -
http://abcathome.com/result.php?resultid=4472
was just short of six hours but result OK and credit granted.
/ 
Next one longer runs on P4 3,2 HT: 5:37h, progressbar go up from 31% to 71% then finished.
/ 
My unit 10h:53m and still 34.700%
/ 
And I've got a big one. After 3h still 3,9%. I hope it's not gonna be that long...
____________
/ And I've got a big one. After 3h still 3,9%. I hope it's not gonna be that long...
Probably it will be shorter. The numbers are very inaccurate on some WUs. Probably it will finish and validate and earn good credits.
/ 11h:54m and 43.200%
/ 35% after 5mins
Then no change for 2hours
/ Hi all,
I too have a long WU - http://abcathome.com/workunit.php?wuid=3372
3hr 24 mins and only 13.5% completed.
Completion due in another 3hrs 47 mins (according to BOINC Manager)
Will leave it to finish off....hopefully soon....!
regards
Tim
/ My first 'long' workunit (ID = 1688) took 3 hrs. 50 sec. on a 2 GHz Athlon64.
Unfortunately, the second result was aborted by the user. I hope whoever will get the third result here will have more patience...
I mean, you could get some 50+ credits for it, so think twice.
And there is only one error result still left...
Regards
Alex
/ My first 'long' workunit (ID = 1688) took 3 hrs. 50 sec. on a 2 GHz Athlon64.
Unfortunately, the second result was aborted by the user. I hope whoever will get the third result here will have more patience...
I mean, you could get some 50+ credits for it, so think twice.
And there is only one error result still left...
Regards
Alex
In the beginning right after the start the parameters for error allowance and
a few others were not set properly, If it might error out, I will run a query to grant the lost credits. It's my mistake, users shouldn't lose credits over it.
/ While I was typing the message, the third result has been handed out. So everything might be allright. But thanks for your concern.
Alex
/ My first 'long' workunit (ID = 1688) took 3 hrs. 50 sec. on a 2 GHz Athlon64.
Wow, we both got 65.99 credits granted for this one, not bad at all.
Alex
/ 
I got a work unit that has been running for 10h30, and only 2.7% far. It is running (or should I say crawling :p ) on a PIII 800MHz. Very old and slow machine, but still. Time to panic, or just be patient?
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ I got a work unit that has been running for 10h30, and only 2.7% far. It is running (or should I say crawling :p ) on a PIII 800MHz. Very old and slow machine, but still. Time to panic, or just be patient?
It will go ok, unlucky that you got such a workunit on this machine.
More important is your memory usage and if it switches with other projects
and you don't leave the app in memory, then a segfault might sometimes occur
and we're all not happy. Can you give the name of the wu?
Then I can estimate what kind it is.
/ Can you give the name of the wu? Then I can estimate what kind it is.
It is abc_wu_393085000_35000
/ Can you give the name of the wu? Then I can estimate what kind it is.
It is abc_wu_393085000_35000
That one is relatively new, and the new ones haven't lasted longer
than 3 hours on my xp 2600+. I'd gamble yours takes not much longer
if you'd a 2600+, but I can't be sure of course. If it just let it run and no other projects interfere it should be ok.
/ I think I am seeing a new problem. My BOINC log shows that abcathome has run twice today but the CPU time has not increased. It is as if no work was done for that time. How can I diagnose this?
Jim
/ I think I am seeing a new problem. My BOINC log shows that abcathome has run twice today but the CPU time has not increased. It is as if no work was done for that time. How can I diagnose this?
Jim
I have a hunch you're seeing a very old and familiar problem that a lot of people run into. It's easily fixed. Actually, nothing is broken, you just need to tweak a setting or 2. Take a look at this thread, I think the advice there will help you.
/ Here's a long one for you on a nice little Pentium D 3.0GHz - 17hrs and at 28.1%. It'll be worth lots of credits when it's done, assuming I can find someone else willing to let it run that long...
/ Mine is 30 hours far now on the PIII. Still at 2.7%. I don't really care. The machine isn't used anyway, so it can run until next Christmas for me. I just hope we don't get one of our famous powercuts...
/ Here's a long one for you on a nice little Pentium D 3.0GHz - 17hrs and at 28.1%. It'll be worth lots of credits when it's done, assuming I can find someone else willing to let it run that long...
What wu is that? I'd be interested to know. I suspect it's one of the first ones
being resent, but it might not.
/ I think I am seeing a new problem. My BOINC log shows that abcathome has run twice today but the CPU time has not increased. It is as if no work was done for that time. How can I diagnose this?
Jim
I have a hunch you're seeing a very old and familiar problem that a lot of people run into. It's easily fixed. Actually, nothing is broken, you just need to tweak a setting or 2. Take a look at this thread, I think the advice there will help you.
OK, I performed the tweaks and I will monitor the results.
Thanks,
Jim
/ Here's a long one for you on a nice little Pentium D 3.0GHz - 17hrs and at 28.1%. It'll be worth lots of credits when it's done, assuming I can find someone else willing to let it run that long...
What wu is that? I'd be interested to know. I suspect it's one of the first ones
being resent, but it might not.
i am guessing it would be abc_wu_393085000_35000
edit i should have refreshed page before posting sorry
____________
/ 
Hi all, I have a WU abc_wu_715470000_35000_0 thats been running for 20hrs 30mins 28.299% with 17hrs 01mins to run I have a P4 3.0ghz HT machine, sounds like I have found one of those LONG WU's ????
I have also just noted that the Time to Complete is getting longer as the progress clock is increasing, now up to 17hrs 07mins ?? Any suggestions??
/ Phew... the work unit on the PIII finally finished after 146,519.04 seconds (over 40 hours). Now let's hope the other result is returned as well, so that the oldie gets his reward :P
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ Hi all, I have a WU abc_wu_715470000_35000_0 thats been running for 20hrs 30mins 28.299% with 17hrs 01mins to run I have a P4 3.0ghz HT machine, sounds like I have found one of those LONG WU's ????
I have also just noted that the Time to Complete is getting longer as the progress clock is increasing, now up to 17hrs 07mins ?? Any suggestions??
Same suggestions that have been given repeatedly to everybody else:
1. In your profile set your preferences to leave apps in memory while suspended.
2. Be patient. The ABC app and the WUs are very stable, the progress indicators do not progress smoothly but the WU will very likely complete and you'll receive good credits.
/ Hi all, I have a WU abc_wu_715470000_35000_0 thats been running for 20hrs 30mins 28.299% with 17hrs 01mins to run I have a P4 3.0ghz HT machine, sounds like I have found one of those LONG WU's ????
I have also just noted that the Time to Complete is getting longer as the progress clock is increasing, now up to 17hrs 07mins ?? Any suggestions??
Same suggestions that have been given repeatedly to everybody else:
1. In your profile set your preferences to leave apps in memory while suspended.
2. Be patient. The ABC app and the WUs are very stable, the progress indicators do not progress smoothly but the WU will very likely complete and you'll receive good credits.
Worked for me once I tweaked my preferences. I am not a patient person but in this case, patience pays off.
Jim
/ We just discussed something in here about altering the checkpointing and progress indication, due to these super surprise workunits,
and I think we have a good idea to change all this, to make progress very accurate
and checkpointing happening every x seconds more or less consistently.
Workunits will still last long, but you know where you're up to, and you won't
have to worry too much about suspending in memory etc.
It's different then the current method which is easier, and sufficed for 10^16
but it appears 10^18 is a different story.
/ We just discussed something in here about altering the checkpointing and progress indication, due to these super surprise workunits,
and I think we have a good idea to change all this, to make progress very accurate
and checkpointing happening every x seconds more or less consistently.
Workunits will still last long, but you know where you're up to, and you won't
have to worry too much about suspending in memory etc.
It's different then the current method which is easier, and sufficed for 10^16
but it appears 10^18 is a different story.
That would be great. Suspending in memory is probably not the biggest problem. Machines that can't run 24/7 and lose a few hours of work each time is worse. You only have to take care if you write every x seconds that disk access doesn't become too frequent. Ideal would be if you could more or less honour Boinc's "write to disk at most every x seconds" setting.
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ We just discussed something in here about altering the checkpointing and progress indication, due to these super surprise workunits,
and I think we have a good idea to change all this, to make progress very accurate
and checkpointing happening every x seconds more or less consistently.
Workunits will still last long, but you know where you're up to, and you won't
have to worry too much about suspending in memory etc.
It's different then the current method which is easier, and sufficed for 10^16
but it appears 10^18 is a different story.
That would be great. Suspending in memory is probably not the biggest problem. Machines that can't run 24/7 and lose a few hours of work each time is worse. You only have to take care if you write every x seconds that disk access doesn't become too frequent. Ideal would be if you could more or less honour Boinc's "write to disk at most every x seconds" setting.
Yeah, with every x seconds I meant boinc's x seconds, of course we want to adapt
to how boinc intended it :)
That's now also the case,
but unfortunately it doesn't get to that point to let boinc checkpoint.
If everything goes as I think it might this will give more precise progress indication than a swiss clock.
/ That would be really nice :)
Now I have two long runs:
both over 7 hours 40 mins now, one with 17,000% stuck, the 2nd with 20,100%
1: abc_wu_477295000_35000_0
2: abc_wu_797720000_35000_1
/ We just discussed something in here about altering the checkpointing and progress indication, due to these super surprise workunits,
and I think we have a good idea to change all this, to make progress very accurate
and checkpointing happening every x seconds more or less consistently.
Workunits will still last long, but you know where you're up to, and you won't
have to worry too much about suspending in memory etc.
It's different then the current method which is easier, and sufficed for 10^16
but it appears 10^18 is a different story.
That would be great. Suspending in memory is probably not the biggest problem. Machines that can't run 24/7 and lose a few hours of work each time is worse. You only have to take care if you write every x seconds that disk access doesn't become too frequent. Ideal would be if you could more or less honour Boinc's "write to disk at most every x seconds" setting.
Yeah, with every x seconds I meant boinc's x seconds, of course we want to adapt
to how boinc intended it :)
That's now also the case,
but unfortunately it doesn't get to that point to let boinc checkpoint.
If everything goes as I think it might this will give more precise progress indication than a swiss clock.
It sounds good for everyone, from older machines with less RAM and slow CPU to newer machines. I have a hunch leaving apps in memory while suspended is causing problems at all projects for hosts with small RAM. It would be good if that setting were not required.
/ Can't wait until checkpointing is sorted out - will take a lot of worry out of seeing long finish times.
I also have one of those long 'surprise' WU's on my AMD 64/3500 (no other project running and suspend to memory set to yes.
WU: abc_wu_845565000_35000_0
9hrs 52mins into work at 36.7% complete - expected time to complete 16hrs 53min - 122 credit on this WU to date showing in BoincView.
____________
/ We just finished the new implementation, and it really looks nice.
I'll throw it into beta soon, and after that, into stable.
You'll get progress precise with long workunits in the order of 1/10000's,
it could in theory be up to 1/10000000 but I think this would be overkill ;)
/ I have a WU abc_wu_464555000_35000 (send 16 Jan 2007 23:58:59 UTC) thats been running at 14.499% with 17hrs 15 mins to run. I have a P4 1,8ghz machine,
running 7/24 with one reboot the last day.
http://abcathome.com/workunit.php?wuid=20793
/ I have a WU abc_wu_464555000_35000 (send 16 Jan 2007 23:58:59 UTC) thats been running at 14.499% with 17hrs 15 mins to run. I have a P4 1,8ghz machine,
running 7/24 with one reboot the last day.
http://abcathome.com/workunit.php?wuid=20793
A tough one too. Try to finish it, tomorrow morning I will put a new version
in stable where you can safely restart/reboot etc and with a precise continuous progress indication without being stuck.
/ It would be nice if people tried to finish the long WU anyway. Otherwise those of us with lots of pending credits on these WU risk losing these, no? Or will the same WU be resent with the new app if work already sent out misses the deadline?
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ It would be nice if people tried to finish the long WU anyway. Otherwise those of us with lots of pending credits on these WU risk losing these, no? Or will the same WU be resent with the new app if work already sent out misses the deadline?
It will be resent with a max of 8 error results atm.
Regeneration is independent of the app version.
Might you notice that due to some unlucky clash of events
your superlong workunit was not granted, it will be granted by
me personally.
/ Caught another overnight, a 7.7hr WU http://abcathome.com/workunit.php?wuid=40156. Longest one I've caught so far.
/ 
abc_wu_668255000_35000 has now been running on a Core Duo for over 19 hours and is showing as being at 70%. How high is that credit cap?? :-)
____________
Join the No.1 Australian ABC@Home Team!
/ abc_wu_668255000_35000 has now been running on a Core Duo for over 19 hours and is showing as being at 70%. How high is that credit cap?? :-)
Not high enough I think. I raised it just in case. Tomorrow morning
the new version will appear in stable that will fix all this.
Now I'm off to bed!
/ 
I have a WU abc_wu_464555000_35000 (send 16 Jan 2007 23:58:59 UTC) thats been running at 14.499% with 17hrs 15 mins to run. I have a P4 1,8ghz machine,
running 7/24 with one reboot the last day.
http://abcathome.com/workunit.php?wuid=20793
ralfi65, I too have a P4 1.8 (mine is using Linux 32bit) my highest time is 5K seconds (note: I just attached it today). In Beta it's done 536 wus at an average of 53 min/wu. There were 3 wus in that test that ran 11,000 seconds(183 min or 3 hours). NONE ran higher than that. Remember this data is from the whole of the beta test and covers MANY MANY different application versions and crunch times.
Also remember Linux is faster than windows (if that's what you're using)
tony
____________
The New Online Helpsytem help is just a call away.
/ My longest unit so far.
http://abcathome.com/workunit.php?wuid=3507
abc_wu_58370000_20000
20,735.25 seconds on core2 6300
so thats about 5hrs 45mins
____________
/ Mine 2 have finished now:
claimed credit: 161.81, time: 67,851.70 sec
claimed credit: 143.23, time: 60,063.80 sec
Pending credit now: 564.94
So my tip: be patient and wait :)
PS: Core2Duo 2,16GHz Laptop running at 1,51GHz (Temperature !!!)
/ 
Im at 5hrs 47mins on my C2D E6400 here at 55% so i hope it speeds through the last bit lol its getting a little long.
____________
/ Tomorrow morning the new version will appear in stable that will fix all this.
Now I'm off to bed!
That's spoken like a true scientist: working on a saturday :p A bit disappointing you stop working and go to sleep at 23h00 already though ;)
Looking forward for the new version. I had to leave the machine in my bedroom on all night to avoid losing 10 hours of work. Spoken like a true Boincer eh ;)
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/
http://abcathome.com/workunit.php?wuid=20793
A tough one too. Try to finish it, tomorrow morning I will put a new version
in stable where you can safely restart/reboot etc and with a precise continuous progress indication without being stuck.
Puuuh! Finished after 102,997.66 Sec
/ 10hrs 24mins and still at 55.9% progress on a C2D lol this is a long one. I have 4 computers networked and on a KVM switch in my bedroom running 24/7 lol. Im an insane BOINCER as its really hard to sleep with all that noise and light from the fans in my c2D.
____________
/ 10hrs 24mins and still at 55.9% progress on a C2D lol this is a long one. I have 4 computers networked and on a KVM switch in my bedroom running 24/7 lol. Im an insane BOINCER as its really hard to sleep with all that noise and light from the fans in my c2D.
Insane :) Can't you move them somewhere else for your health?
If you finish these, and you automatically get 1.01, you know exactly how
long they are going to last.
/ No can do on the move but you grow used to it eventually lol. Its past 10hrs 50mins now without any movement. From what i saw the other cruncher finished this unit in 8hrs on an E6600 im wonder how heavily it was overclocked lol. Knowing how long they last would be nice lol.
____________
/ Tomorrow morning the new version will appear in stable that will fix all this.
Now I'm off to bed!
That's spoken like a true scientist: working on a saturday :p A bit disappointing you stop working and go to sleep at 23h00 already though ;)
Looking forward for the new version. I had to leave the machine in my bedroom on all night to avoid losing 10 hours of work. Spoken like a true Boincer eh ;)
I try to check things regularly and try to fix problems fast
when I can, all the users are dedicating precious computing time,
and if I just let it sit there for days and not respond it's not good
and without much respect. Also, it's a good way to know what is going
on and react on it fast, before the entire project runs of by itself.
If users are not happy, there's usually something wrong
with the project or design of it, and needs to be adjusted.
/ Im really beginning to think this WU has errored out as im past 11 hours and unless the E6600 is heavily overclocked my E6400 shouldn't be this much slower than it.
Im about to go to bed now and try this sleep thing people always talk about should i kill it if its not finished by morning?
____________
/ If you don't suspend it or switch it I can guarantee it will finish.
I would suggest bite through this 'rotten apple' and you will get 1.01
and this is history, but I can imagine if it doesn't finish after xx hours
you cancel it.
This workunit is really going to last from what I see from the returned result, I will calculate for you how long approx. without suspending, if you hang on a minute :)
EDIT: When I look at your host, and use how fast it was on other long workunits,
it is going to last in total : 13.2 hours !
/ Finished while i was asleep and credit was granted. That was a long one lol. Next task to work out why my computer is so slow compared to that E6600
____________
/ Finished while i was asleep and credit was granted. That was a long one lol. Next task to work out why my computer is so slow compared to that E6600
You were up against a approx 3.5GHz processor.
____________
Team Boinc@Australia.
/ Overclocked? Also for my computer is now estimating 9hr 40mins a WU for ABC so im having problems keeping enough work on hand. Anyway i can fix this without restarting boinc? If i do that i generally have to restart the computer asthe manager stops talking to the client and calls incorrect password.
____________
/ So does 1 day 05:38:00 total time constitute a WU to be aborted?
It has been running now for 15:14:30 and so far is still stuck on 14.599% - it has been stuck at this point today for over 10 hrs
WU id: abc_wu_1516655000_35000_0 (abc-finder 1.00)
/ Has anyone else completed the task?
Can we get the Wu number and what sort of computer is this on?
If something can take 13hrs on my C2D it could easily take more than a day on a p4 or a celeron.
____________
/ WU ID: 50853
it finally finished @ 19:27 AEDST time - total time 16:51:32
/ WU
total time: 19:33h, thats long :o
/ Really long yes. I'm glad you guys complete it though, it's not easy to let it sit
there with 1.00 and see the progress get stuck at some point with no idea
how long it will take.
/ Actually as someone who has crunched for RCN for a long time its actually nowhere near as bad lol. They don't give any idea of progress and my record is 202hrs on the celery 700 and 131hrs on the C2D all without checkpoints so as you can imagine once they pass 8 hours you really sweat the power not going out lol.
____________
/ Henk, the application 1.01 is working well for me. Steady progress in % done. And perfectly honouring my "x seconds" setting, which is 180 in my case. You're doing a great job in this project ;)
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ Yeah 1.01 is great now if only RCN could get their app to work like that lol. But don't help them lol i might head back there again if you do lol.
I like this app but for some reason im still running RCN at 50% (on one core) all the time even though the resource share is 10000 ABC 1 RCN lol. Gotta love BOINC 5.8.x
I would just run ABC alone but i don't trust one project to stay up all the time and always run a backup although 5.8.1 is beginning to make me regret this.
____________
/ 
Wow!!! I was checking out the progress of my work units, and surprise, surprise, my ABC@home workunit's pregress was actually moving every second. Thank you very much Hendrik for the improvement.
/ Wow!!! I was checking out the progress of my work units, and surprise, surprise, my ABC@home workunit's pregress was actually moving every second. Thank you very much Hendrik for the improvement.
No problem :) Now the only thing I want to come soon is that the workunits become
more regular, we'll see how that goes.
/ 
Now the only thing I want to come soon is that the workunits become
more regular, we'll see how that goes.
I look forward to it as well. The big variation in work unit length gets the BOINC scheduler all confused. It wants to download a day's worth of work but doesn't know whether that's 1 work unit or 50.
I suspect there is a mathematical reason behind the difference, but can't quite work out why (I didn't do well at maths when I went to the HAVO all those decades ago). Care to share?
____________
Join the #1 Aussie Alliance on ABC@Home
/ I've got two wu's which didn't progress.
The processor time stood still and my cpu was idling.
I've cancelled those two.
Any problems on certain wu's??
74736
76455
/ What version of BOINC are you using? sometimes the 5.8.x client does this. I found a suspend then resume project is one fix and another is restart BOINC. If all else fails reboot.
____________
/ Now the only thing I want to come soon is that the workunits become
more regular, we'll see how that goes.
I look forward to it as well. The big variation in work unit length gets the BOINC scheduler all confused. It wants to download a day's worth of work but doesn't know whether that's 1 work unit or 50.
I suspect there is a mathematical reason behind the difference, but can't quite work out why (I didn't do well at maths when I went to the HAVO all those decades ago). Care to share?
The radicals are in this range still fairly low, meaning a lot of numbers
have to be scanned of (i.e. low primes occur more in numbers up to
a fixed bound than do bigger primes, for example a lot of numbers
can be divisible by 5 up to 100, not less are divisible by say 37).
/ I have here a long one as well.
The strange thing is when I shutdown my computer ,and restart him a day later it seems to restart from 0 is this normal ??
Till now no one has completed the work id : abc_wu_1406055000_35000
http://abcathome.com/workunit.php?wuid=47693
/ I have here a long one as well.
The strange thing is when I shutdown my computer ,and restart him a day later it seems to restart from 0 is this normal ??
Till now no one has completed the work id : abc_wu_1406055000_35000
http://abcathome.com/workunit.php?wuid=47693
What application version is running the work unit? If it is 1.00, then that can be expected, because the checkpoints are often very far apart. If it's 1.01, I'm afraid I'll have to pass :P
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ I have here a long one as well.
The strange thing is when I shutdown my computer ,and restart him a day later it seems to restart from 0 is this normal ??
Till now no one has completed the work id : abc_wu_1406055000_35000
http://abcathome.com/workunit.php?wuid=47693
What application version is running the work unit? If it is 1.00, then that can be expected, because the checkpoints are often very far apart. If it's 1.01, I'm afraid I'll have to pass :P
It's still 1.00 , but how ca nyou upgrade to the newer release ?
Is it connected with your BOINC client , or can you just place some newer files on your current client ?
____________
Member of BOINC.BE
/ The next time you download new work you will also download the new app automatically. Once you finish the existing work under the old app, you won't have this problem any more.
____________
Join the No.1 Australian ABC@Home Team!
/ @kdr_98: While Boinc is not running you could probably modify client_state.xml manually and look for a block like this:
<app_name>abc-finder</app_name>
<version_num>100</version_num>
<file_ref>
<file_name>abc-finder_1.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
</app_version>
And replace 100 and 1.00 by 101 and 1.01. Make sure you have a 1.01 WU downloaded already, so that you have the abc-finder_1.01_windows_intelx86.exe. I'm not sure that will be enough, or even work. You may also have to find the right directory under slots, copy the .exe there and edit init_data.xml there. Modify in
This is not guaranteed to work :P Don't try this at home. Or do?
____________
BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning
Tutta55's Lair
/ That might make your result invalid, changing to 1.01. If you do it, be sure
to delete the abc_state file.
/ That might make your result invalid, changing to 1.01. If you do it, be sure
to delete the abc_state file.
Your right about the new version , all the new are in the version 1.01
Is there a way to convert 1.00 blocks to 1.01.
Since the file size is not tight of the above procedure I doubt it may work.
I tried the procedure above , without any result.
Had to detach the project en reattach the project afterwards.
Now i'm running the new client 1.01
____________
Member of BOINC.BE
/ That might make your result invalid, changing to 1.01. If you do it, be sure
to delete the abc_state file.
Your right about the new version , all the new are in the version 1.01
Is there a way to convert 1.00 blocks to 1.01.
They are called work units or WUs, not blocks :-)
There is no need to convert the WUs because they are the same under 1.00 and 1.01. It's just that BOINC thinks the old WUs must be processed by the abc-finder 1.00 application. In reality the WUs can be processed by abc-finder 1.01 too. All you need to do is tell BOINC to use 1.01. The procedure for telling BOINC to use 1.01 is given in posts above.
If you don't want to use the above procedure (it is a bit tricky and may not work) then you have 2 options:
option 1
Just abort the 1.00 WU. It will be issued to another cruncher under 1.01, no big problem.
option 2
Temporarily suspend all other projects and set ABC to "no new work units". Then just let your computer run continuously and don't interrupt the 1.00 WU until the 1.00 WU finishes processing. Then resume the other projects and set ABC to "accept work units".
/ Well I am still cleaning out my supply of 1.0 units, only a few left.
Just finished a killer unit. 12hrs10min and a core2duo 6300
http://abcathome.com/workunit.php?wuid=51302
____________
/ This wu;
1718430000-3500-1
Has been under way now for over 57 hrs. The other recipient finished in under 6 min. It is at 98% with estimated 5 hr completion.
I will run this until tomorrow afternoon and delete if not finished. Over 3 days work is enough:D
____________
208.55Ghz Home Owned and Operated Crunching Power
/ I have suspended the below mentioned wu @ 67 hrs.
Do you want me to delete it or is there information that I can extract and send to be analyzed??
____________
208.55Ghz Home Owned and Operated Crunching Power
/ My poor celery 700 has caught a nice long WU. 36hrs so far for 90%. Its another reason i should be retiring this poor old workhorse.
____________
/ I have found my problem; The ram was erroring.
Still have this wu in cache, Hendrik, do I need to delete this??or is it of any use to you?
____________
208.55Ghz Home Owned and Operated Crunching Power
/ Now that was a long WU. I couldnt imagine doing that under 1.00 it was bad enough as it was.
http://abcathome.com/workunit.php?wuid=104241
____________
/ ... it was bad enough as it was.
Huh? I don't understand. One of my slow, old machines caught a 39 hour WU a few days ago. To be honest, I didn't see it as a bad experience at all. The machine did all the work while I played slap and tickle with the missus. What, exactly, did you find "bad" about that WU? Did you have to sit there for 36 hours and spin the disk by hand? Don't you think your words tend to scare away new crunchers rather than attract and encourage them?
Complaining about these very few long WUs we are getting isn't going to help anybody. Hendrik has already explained that making them shorter will take a huge effort and introduce other complications. He has already explained that all we need to do is just be patient and in a while there will be no more long WUs. In the meantime, 99% of the few long WUs we get process just fine.
/ ... it was bad enough as it was.
Huh? I don't understand. One of my slow, old machines caught a 39 hour WU a few days ago. To be honest, I didn't see it as a bad experience at all. The machine did all the work while I played slap and tickle with the missus. What, exactly, did you find "bad" about that WU? Did you have to sit there for 36 hours and spin the disk by hand? Don't you think your words tend to scare away new crunchers rather than attract and encourage them?
Complaining about these very few long WUs we are getting isn't going to help anybody. Hendrik has already explained that making them shorter will take a huge effort and introduce other complications. He has already explained that all we need to do is just be patient and in a while there will be no more long WUs. In the meantime, 99% of the few long WUs we get process just fine.
I agree...fully.
Jim
/ You try and keep a steam powered dinosaur like the Celery 700 of mine up for that long with thunderstorms around. It the only PC i don't have a UPS on as i couldnt justify $140 to protect it. Its already errored out a few big Wu's in the past so unlike my other machines that im fairly certain will complete the WU safely this one i always have doubts in the back of my mind. Im more worried about having one fail and some other poor cruncher who runs there PC maybe and hour or two a day getting it than anything else.
Actually if you read my previous posts ive already done some monsters here and even more of them in RCN. In fine weather no problems but as soon as it rains my power gets mighty unpredictable here and hence its a scary situation. Last major set of storms we had i lost a hard disk and one of the RAM slots on the old celery so i have a right to be scared lol.
Now if there was a way to move long WU's it would be great i have no issue with workunits running even a week or two on my C2D
____________
/ Celery 700??? and a Coppermine to boot??? WOW many is the day, I've dreamed about somthing that powerful. You lucky dog. Here I sit with a Celery 500 nocona,, Sob...Sob...
OK, so I know what you mean about "pondering it's retirement".(it's currently running rosetta)
/ Update:)
After thinking awhile, I just restarted the 57 hr behemoth and it has restarted and completed itself in 7 min:)
Just information.
@KIM, I was not complaining by any means, just trying to give information to Hendrik. I personally don't care how long the work lasts....just that it completes itself.
____________
208.55Ghz Home Owned and Operated Crunching Power
/
@Mike, I didn't consider your reports to be complaining. The 57 hours you initially reported would be a record and your co-cruncher finished it in 6 minutes. Wierd things like that definitely should be reported, IMHO.
Just wondering if the science app, abc-finder, was continually restarting during that 57 hour period? There was another report of that happening and it happened to me once too, yours could be a third instance. Could you check the log file, stdoutae.txt, search for "restart" or maybe "re-start"?
/ HI, No restarts, I think it just never got started and was trying to start for 57hrs. The timer kept running. I fixed the ram and everything seems OK now. If anything changes, I'll post.
____________
208.55Ghz Home Owned and Operated Crunching Power
/ abc_wu_72804100000_5000_0 running 7:15:19 62,201%
Need more claasical CDs :-))
/