Not sure what is happening on my computer (BOINC 4.44 MacNN, 10.3.9). Ever since I installed Einstein client 0.08 (which was yesterday night), things have gotten way too slow. In 19+ hours, the client claims it has completed only 2.3% of this WU . On average, Einstein has been using 92% of the CPU for the last 19 hours. The unoptimized client used to take 20 hours for a WU, while the beta versions (0.02 and 0.05) used to take slightly more than 10 hours/WU.
Has any body else noticed this with 0.08? If not, is someone willing to help me figure out the problem? Currently, the computer is not attached to any other project. Thanks.
Here's my new problem. I haven't received any new WUs since upgrading to Einstein .08. Is there something going on with the server. I have three project attached and I am almost out of WUs. Two projects are empty, Einstein and SZTAKI Desktop Grid. Seti@home seems to be the only one downloading any new work. Is anyone else having this problem?
1. I can't reproduce your problem either. However I am currently running a development Client (4.71) which might behave a bit differently. Anybody else seen this?
2. In any case this seems to be not a problem of the App, but of the Client.
3. It may also indicate a software or hardware problem on your machine. Which OS version are you running?
Here's my new problem. I haven't received any new WUs since upgrading to Einstein .08. Is there something going on with the server. I have three project attached and I am almost out of WUs. Two projects are empty, Einstein and SZTAKI Desktop Grid. Seti@home seems to be the only one downloading any new work. Is anyone else having this problem?
I looked at your host, #358216, in the scheduler log. It's contacted the scheduler a couple of times in the past day, but not requested ANY work. This may be because of the new 'long term debt' policies in the BOINC client; on your machine Einstein@Home may have built up a long term debt compared with SETI@Home. I suggest you look in the 'Problems and Bug reports' forum to see discussion of this. I don't understand it well but know that the normal advice is 'just wait a few days and it will sort itself out'.
Not sure what is happening on my computer (BOINC 4.44 MacNN, 10.3.9). Ever since I installed Einstein client 0.08 (which was yesterday night), things have gotten way too slow. In 19+ hours, the client claims it has completed only 2.3% of this WU . On average, Einstein has been using 92% of the CPU for the last 19 hours. The unoptimized client used to take 20 hours for a WU, while the beta versions (0.02 and 0.05) used to take slightly more than 10 hours/WU.
Has any body else noticed this with 0.08? If not, is someone willing to help me figure out the problem? Currently, the computer is not attached to any other project. Thanks.
Hmmm, weird. The 0.08 app has only a single tiny difference from 0.05, which should not have this effect. So I have no idea what's wrong. Could you start up the 'Activity Monitor' and look carefully at the process list to be sure that there is nothing else running on your system? Eg extra copies of BOINC or of the BOINC manager, for example?
I've got a Dual 1.0 GHz G4, BOINC Advanced GUI 4.43, and the 0.08 app. Nothing seems to be wrong aside from the "running" WU and the WU showing a gain in CPU time not always matching. I've seen this without the beta app, so I assume this is BOINC-related because a restart of BOINC fixes this.
Could you please describe this problem in some more detail? I'm not aware of it. Also please describe in more detail how you fix it. How do you restart BOINC?
I've got a Dual 1.0 GHz G4, BOINC Advanced GUI 4.43, and the 0.08 app. Nothing seems to be wrong aside from the "running" WU and the WU showing a gain in CPU time not always matching. I've seen this without the beta app, so I assume this is BOINC-related because a restart of BOINC fixes this.
Could you please describe this problem in some more detail? I'm not aware of it. Also please describe in more detail how you fix it. How do you restart BOINC?
What I mean is that the BOINC Manager status column sometimes says "running" for a WU (usually Einstein) even though the CPU time says "---" and the progress says "0.00%." Activity Monitor says that an Einstein process is indeed running so I've assumed it was just a BOINC Manager display bug. After all, sometimes the opposite problem occurs when I get three WUs running on a dual proc machine because Einstein just won't let go. In this case BOINC Manager lists the Einstein as "Paused" even though it is actually running and the CPU time keeps updating. If I quit (cmd-Q) and restart BOINC Manager, the GUI then correctly displays the status of each WU and correctly limits the running WUs to two.
In the first case above with the running WU showing no progress, after a restart the WU instantly has what I presume to be the correct CPU time and progress. It's really no big deal and does not seem to affect the validity of any WU. I guess the only downside is that sometimes BOINC forgets to start a WU when it's confused and I end up with my dual proc machine only doing one WU. Such is life.
I may be experiencing the same (or a similar) problem as Alan Ng. This morning, I looked at Activity Monitor on my 1 GHz PowerBook G4, OS X 10.3.9, BOINC 4.44 Super, and E@H .08, as CLI and saw in the little graph that roughly 30% of the CPU was "user", 60% was "system", and 10% was "nice". "Nice" is normally where the BOINC clients all show up. Ratios of these three are normally 1%, 1%, and 98%, if nothing else is running. When I looked at the tabular data, it said BOINC was using nothing, E@H was using 95%+, and various other processes a touch. I had left Eudora 6.1 on all night, so I quit it, made sure nothing else was running, and looked at Activity Monitor again. Nothing had changed in the tabular data, but in the little Dock Graph, "user" had changed to maybe 10-15%, "system" had remained about the same at 60%, and "nice" had risen to roughly 25%. I killed BOINC (cmd-C) in Terminal, then restarted it. E@H resumed running, and in the graph it showed "user" and "system" as their normal 1-2% and E@H as it's normal 95-98%. Tabular data showed only E@H, as SETI and CPDN had been removed from memory when i quit BOINC. Since then, E@H has run a couple of hours, let CPDN run an hour, and E@H again for a couple of hours. SETI won't begin running for another 4 or 5 hours, though.
"Nice" continues to show 95% or so in the Dock graph.
There were no indications in the Terminal Log that anything unusal was going on. Unfortunately, I didn't save the log. If this happens again, I will save it.
Hmmm, weird. The 0.08 app has only a single tiny difference from 0.05, which should not have this effect. So I have no idea what's wrong. Could you start up the 'Activity Monitor' and look carefully at the process list to be sure that there is nothing else running on your system? Eg extra copies of BOINC or of the BOINC manager, for example?
I did check my activity monitor; nothing else was running. I still couldn't figure out the reason for the slowness. I tried exiting BOINC and restarting it again with the same results. I thought the client had gone into an infinte loop. I finally rebooted the computer. Things have come back to their normal speed since. I haven't uploaded the completed result yet. Perhaps, one can find the cause of the slowness by looking at the results? Thanks for your help.
In response to my earlier post describing the failure of BOINC standard GUI 4.43 to suspend and then return to "Run based on preferences."
I have now also confirmed this behavior on a different machine. Again, the machine I described earlier as doing this is: http://einsteinathome.org/host/205881
I'll quote my previous post to reuse that description of the observed behavior:
Quote:
Issuing "Suspend" now works as desired, and as you [BM] describe above.
However, when I then choose "Run based on preferences," even after waiting a minute or so, the WU remains in "Paused" status and Activity Monitor confirms that it (and boinc) are still inactive. My cooling fan remains idle, too.
This time, on this new machine (a 3-week old Mac mini), I took the additional step of subsequently setting BOINC to "Run always." BOINC does not respond to this: the "Work" tab and Activity Monitor show BOINC as still completely paused.
Then if I quit and restart BOINC everything returns to normal behavior.
Not sure what is happening on
)
Not sure what is happening on my computer (BOINC 4.44 MacNN, 10.3.9). Ever since I installed Einstein client 0.08 (which was yesterday night), things have gotten way too slow. In 19+ hours, the client claims it has completed only 2.3% of this WU . On average, Einstein has been using 92% of the CPU for the last 19 hours. The unoptimized client used to take 20 hours for a WU, while the beta versions (0.02 and 0.05) used to take slightly more than 10 hours/WU.
Has any body else noticed this with 0.08? If not, is someone willing to help me figure out the problem? Currently, the computer is not attached to any other project. Thanks.
Here's my new problem. I
)
Here's my new problem. I haven't received any new WUs since upgrading to Einstein .08. Is there something going on with the server. I have three project attached and I am almost out of WUs. Two projects are empty, Einstein and SZTAKI Desktop Grid. Seti@home seems to be the only one downloading any new work. Is anyone else having this problem?
MacStef
G4 DP 1GHz 1.5GB Ram
OSX 10.3.9
Boinc 4.44
Seti 4.30
Einstein 0.08
SZTAKI Desktop Grid 4.01
RE: Alan, 1. I can't
)
Here's this machine:
http://einsteinathome.org/host/205881
Are you a musician? Join the Musicians team.
Meet the Musicians
RE: Here's my new problem.
)
I looked at your host, #358216, in the scheduler log. It's contacted the scheduler a couple of times in the past day, but not requested ANY work. This may be because of the new 'long term debt' policies in the BOINC client; on your machine Einstein@Home may have built up a long term debt compared with SETI@Home. I suggest you look in the 'Problems and Bug reports' forum to see discussion of this. I don't understand it well but know that the normal advice is 'just wait a few days and it will sort itself out'.
Bruce
Director, Einstein@Home
RE: Not sure what is
)
Hmmm, weird. The 0.08 app has only a single tiny difference from 0.05, which should not have this effect. So I have no idea what's wrong. Could you start up the 'Activity Monitor' and look carefully at the process list to be sure that there is nothing else running on your system? Eg extra copies of BOINC or of the BOINC manager, for example?
Director, Einstein@Home
RE: I've got a Dual 1.0 GHz
)
Could you please describe this problem in some more detail? I'm not aware of it. Also please describe in more detail how you fix it. How do you restart BOINC?
Director, Einstein@Home
RE: RE: I've got a Dual
)
What I mean is that the BOINC Manager status column sometimes says "running" for a WU (usually Einstein) even though the CPU time says "---" and the progress says "0.00%." Activity Monitor says that an Einstein process is indeed running so I've assumed it was just a BOINC Manager display bug. After all, sometimes the opposite problem occurs when I get three WUs running on a dual proc machine because Einstein just won't let go. In this case BOINC Manager lists the Einstein as "Paused" even though it is actually running and the CPU time keeps updating. If I quit (cmd-Q) and restart BOINC Manager, the GUI then correctly displays the status of each WU and correctly limits the running WUs to two.
In the first case above with the running WU showing no progress, after a restart the WU instantly has what I presume to be the correct CPU time and progress. It's really no big deal and does not seem to affect the validity of any WU. I guess the only downside is that sometimes BOINC forgets to start a WU when it's confused and I end up with my dual proc machine only doing one WU. Such is life.
derekm
Team MacAddict
I may be experiencing the
)
I may be experiencing the same (or a similar) problem as Alan Ng. This morning, I looked at Activity Monitor on my 1 GHz PowerBook G4, OS X 10.3.9, BOINC 4.44 Super, and E@H .08, as CLI and saw in the little graph that roughly 30% of the CPU was "user", 60% was "system", and 10% was "nice". "Nice" is normally where the BOINC clients all show up. Ratios of these three are normally 1%, 1%, and 98%, if nothing else is running. When I looked at the tabular data, it said BOINC was using nothing, E@H was using 95%+, and various other processes a touch. I had left Eudora 6.1 on all night, so I quit it, made sure nothing else was running, and looked at Activity Monitor again. Nothing had changed in the tabular data, but in the little Dock Graph, "user" had changed to maybe 10-15%, "system" had remained about the same at 60%, and "nice" had risen to roughly 25%. I killed BOINC (cmd-C) in Terminal, then restarted it. E@H resumed running, and in the graph it showed "user" and "system" as their normal 1-2% and E@H as it's normal 95-98%. Tabular data showed only E@H, as SETI and CPDN had been removed from memory when i quit BOINC. Since then, E@H has run a couple of hours, let CPDN run an hour, and E@H again for a couple of hours. SETI won't begin running for another 4 or 5 hours, though.
"Nice" continues to show 95% or so in the Dock graph.
There were no indications in the Terminal Log that anything unusal was going on. Unfortunately, I didn't save the log. If this happens again, I will save it.
C
Join Team MacNN
RE: Hmmm, weird. The 0.08
)
I did check my activity monitor; nothing else was running. I still couldn't figure out the reason for the slowness. I tried exiting BOINC and restarting it again with the same results. I thought the client had gone into an infinte loop. I finally rebooted the computer. Things have come back to their normal speed since. I haven't uploaded the completed result yet. Perhaps, one can find the cause of the slowness by looking at the results? Thanks for your help.
In response to my earlier
)
In response to my earlier post describing the failure of BOINC standard GUI 4.43 to suspend and then return to "Run based on preferences."
I have now also confirmed this behavior on a different machine. Again, the machine I described earlier as doing this is:
http://einsteinathome.org/host/205881
Now I have installed einstein 0.08 and observed the same behavior on another machine:
http://einsteinathome.org/host/335019
I'll quote my previous post to reuse that description of the observed behavior:
This time, on this new machine (a 3-week old Mac mini), I took the additional step of subsequently setting BOINC to "Run always." BOINC does not respond to this: the "Work" tab and Activity Monitor show BOINC as still completely paused.
Then if I quit and restart BOINC everything returns to normal behavior.
Are you a musician? Join the Musicians team.
Meet the Musicians