Now this is getting difficult. Early prognosis warn me that if i continue doing E@H with S@H (50:50) share, i wont make it before deadline. I probably would, as those predictions are very inaccurate in my example, but running 24\\7 i`d need around 110h to complete one WU. Ok.. this is still roughly 4.5 day, but as i say, i often use this PC, so it`s usualy idle only when i sleep.
All of this makes krunching both projects very unsafe, regarding the short deadline. I`m doing the second WU right now, will see how long will it take (i dont suspect a significant change here).
I can only beg to fix that Windows/AMD compiler bug... 25% in my case is almost 14h wasted!!! This is more than 3 SETI WU`s wasted per one E@H WU!
I may be forced to suspend E@H on both my hosts (both are Windows/AMD) and get back only when bug is fixed (and app possibly optimized). Please do not get this as a threat or ultimatum, this is pure math and effciency. My cpu isn`t as fast as many here, so i need to be efficient.
I may be forced to suspend E@H on both my hosts (both are Windows/AMD) and get back only when bug is fixed (and app possibly optimized). Please do not get this as a threat or ultimatum, this is pure math and effciency. My cpu isn`t as fast as many here, so i need to be efficient.
BOINC will eventually go into EDF (Earliest Deadline First) and will work exclusively on the Einstein units until they've been completed.
Quote:
4/26/2007 12:40:10 PM||Using earliest-deadline-first scheduling because computer is overcommitted.
It is still possible though, depending on how many units you downloaded, that even with that the units may not complete prior to the deadline. Since you appear to have only 1 unit out on both of your systems, you should be fine with just letting it enter EDF...
I can only beg to fix that Windows/AMD compiler bug... 25% in my case is almost 14h wasted!!! This is more than 3 SETI WU`s wasted per one E@H WU!
I have just stopped taking new wu from E@H until the problem is fixed. I will let the "QUE" work itself out. I will also suspend E@H after the last one uploads so the computer will take on additional work from the other projects. All 3 of my computers are AMD/window units.
Anyone else have any better idea's?
[pre][= blue]SETI@home classic workunits = 5,906 with CPU time of 60,377 hours[/][/pre]
I got errors for 2 wus too. They stopped working after 15 and 18.5 hours of computation. The error code was "process got signal 11" WU 1 WU 2
For "WU 2" the message in BOINC was:
Quote:
Fri 27 Apr 2007 06:34:43 PM CEST|lhcathome|Sending scheduler request to http://lhcathome.cern.ch/lhcathome_cgi/cgi
Fri 27 Apr 2007 06:34:43 PM CEST|lhcathome|Reason: To fetch work
Fri 27 Apr 2007 06:34:43 PM CEST|lhcathome|Requesting 86400 seconds of new work
Fri 27 Apr 2007 06:34:48 PM CEST|lhcathome|Scheduler request succeeded
Fri 27 Apr 2007 06:34:48 PM CEST|lhcathome|No work from project
Fri 27 Apr 2007 06:34:48 PM CEST|lhcathome|Deferring scheduler requests for 12 minutes and 37 seconds
Fri 27 Apr 2007 06:45:32 PM CEST|Einstein@Home|Restarting task h1_0224.15_S5R2__48_S5R2c_0 using einstein_S5R2 version 414
Fri 27 Apr 2007 06:45:32 PM CEST|QMC@HOME|Pausing task three_bench19_jsch2005s22exp.321_0 (left in memory)
Fri 27 Apr 2007 06:45:34 PM CEST|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
Fri 27 Apr 2007 06:45:34 PM CEST|Einstein@Home|Reason: To fetch work
Fri 27 Apr 2007 06:45:34 PM CEST|Einstein@Home|Requesting 6551 seconds of new work
Fri 27 Apr 2007 06:45:39 PM CEST|Einstein@Home|Scheduler request succeeded
Fri 27 Apr 2007 06:45:41 PM CEST||Rescheduling CPU: files downloaded
Fri 27 Apr 2007 06:45:44 PM CEST|Einstein@Home|Unrecoverable error for result h1_0224.15_S5R2__48_S5R2c_0 (process got signal 11)
Fri 27 Apr 2007 06:45:44 PM CEST|Einstein@Home|Deferring scheduler requests for 1 minutes and 0 seconds
Fri 27 Apr 2007 06:45:44 PM CEST||Rescheduling CPU: application exited
Fri 27 Apr 2007 06:45:44 PM CEST|Einstein@Home|Computation for task h1_0224.15_S5R2__48_S5R2c_0 finished
Fri 27 Apr 2007 06:45:44 PM CEST|Einstein@Home|Starting task h1_0224.15_S5R2__28_S5R2c_1 using einstein_S5R2 version 414
So Einstein@home restarted the work unit, QMC@home stopped working, Einstein@home started with a request to the scheduler and after downloading some files the error occurred.
I hope this may help debugging.
Wow.... the Floating Point Speed is taking a steep dive...!!!
Any ideas why?
acording to the server stats page, the flops count is based off of RAC, and with a 25-40% decrease in credits/hour for higher end CPUs this is a rather large hit.
I can only beg to fix that Windows/AMD compiler bug... 25% in my case is almost 14h wasted!!! This is more than 3 SETI WU`s wasted per one E@H WU!
I have just stopped taking new wu from E@H until the problem is fixed. I will let the "QUE" work itself out. I will also suspend E@H after the last one uploads so the computer will take on additional work from the other projects. All 3 of my computers are AMD/window units.
I've finished the first two S5R2 units and am half way through the third without any trouble so far. I'm running an old AMD 850 and taking about 50 hours per unit time. Is it just the newer machines that are overclocked that are having trouble?
(edit) is running multiple projects not helping, I run Einstein only.
I can only beg to fix that Windows/AMD compiler bug... 25% in my case is almost 14h wasted!!! This is more than 3 SETI WU`s wasted per one E@H WU!
I have just stopped taking new wu from E@H until the problem is fixed. I will let the "QUE" work itself out. I will also suspend E@H after the last one uploads so the computer will take on additional work from the other projects. All 3 of my computers are AMD/window units.
Boinc Master... no idea. I have two new boxes, but none of them is overclocked. I haven't had a single client error so far on either Windows or Linux, and those boxes are really different ^^ one is an AMD running Debian Linux (atm) with a rather new Geforce video card, the notebook is an Intel dual-core with an ATI card running Windows XP... the crappy pre-installed home OEM version, even. So, I have no idea what helps or doesn't help. But Einstein has shared computing time with PrimeGrid, SETI and DRTG here and that doesn't seem to have caused any problems. Now they are both running Einstein only, though.
Now this is getting
)
Now this is getting difficult. Early prognosis warn me that if i continue doing E@H with S@H (50:50) share, i wont make it before deadline. I probably would, as those predictions are very inaccurate in my example, but running 24\\7 i`d need around 110h to complete one WU. Ok.. this is still roughly 4.5 day, but as i say, i often use this PC, so it`s usualy idle only when i sleep.
All of this makes krunching both projects very unsafe, regarding the short deadline. I`m doing the second WU right now, will see how long will it take (i dont suspect a significant change here).
I can only beg to fix that Windows/AMD compiler bug... 25% in my case is almost 14h wasted!!! This is more than 3 SETI WU`s wasted per one E@H WU!
I may be forced to suspend E@H on both my hosts (both are Windows/AMD) and get back only when bug is fixed (and app possibly optimized). Please do not get this as a threat or ultimatum, this is pure math and effciency. My cpu isn`t as fast as many here, so i need to be efficient.
RE: I may be forced to
)
BOINC will eventually go into EDF (Earliest Deadline First) and will work exclusively on the Einstein units until they've been completed.
It is still possible though, depending on how many units you downloaded, that even with that the units may not complete prior to the deadline. Since you appear to have only 1 unit out on both of your systems, you should be fine with just letting it enter EDF...
RE: I can only beg to fix
)
I have just stopped taking new wu from E@H until the problem is fixed. I will let the "QUE" work itself out. I will also suspend E@H after the last one uploads so the computer will take on additional work from the other projects. All 3 of my computers are AMD/window units.
Anyone else have any better idea's?
I got errors for 2 wus too.
)
I got errors for 2 wus too. They stopped working after 15 and 18.5 hours of computation. The error code was "process got signal 11"
WU 1
WU 2
For "WU 2" the message in BOINC was:
So Einstein@home restarted the work unit, QMC@home stopped working, Einstein@home started with a request to the scheduler and after downloading some files the error occurred.
I hope this may help debugging.
Greetings, Santas little helper
RE: Wow.... the Floating
)
acording to the server stats page, the flops count is based off of RAC, and with a 25-40% decrease in credits/hour for higher end CPUs this is a rather large hit.
RE: RE: I can only beg
)
view this:
my post
Well you know how it
)
Well you know how it works,especially with the S5R2's that take longer (for good reason)
We just have to wait for others that may have slower processors to finish ones we already have finished.
I have finished 18 so far but 7 are still pending waiting for another machine out there some where to also finish and turn them in.
I still haven't tested my AMD 3200.......having trouble getting it to connect to my satellite isp.
I've finished the first two
)
I've finished the first two S5R2 units and am half way through the third without any trouble so far. I'm running an old AMD 850 and taking about 50 hours per unit time. Is it just the newer machines that are overclocked that are having trouble?
(edit) is running multiple projects not helping, I run Einstein only.
Mrs Miggins - A lady of uncommon refinement
RE: RE: RE: I can only
)
Which file do you insert this code into or what code this should it replace.
Boinc Master... no idea. I
)
Boinc Master... no idea. I have two new boxes, but none of them is overclocked. I haven't had a single client error so far on either Windows or Linux, and those boxes are really different ^^ one is an AMD running Debian Linux (atm) with a rather new Geforce video card, the notebook is an Intel dual-core with an ATI card running Windows XP... the crappy pre-installed home OEM version, even. So, I have no idea what helps or doesn't help. But Einstein has shared computing time with PrimeGrid, SETI and DRTG here and that doesn't seem to have caused any problems. Now they are both running Einstein only, though.