> Note the words in Parenthesis (left in memory) You can turn this off in the
> preferences. The app may still show in Activity Monitor but it should not
> show any cpu usage. If you turn off the "keep in memory" in preferences, it
> should disappear from the activity monitor when paused.
>
I agree it should not be showing CPU usage, but it does. Instead of pausing and giving 100% of the CPU usage to SETI, E&H only gives up 50% and keeps 50% for itself. This is not RAM space - it's actually incrementing CPU usage time.
Just in case the optimized Mac G4 client might be the problem, I took it out and reloaded the standard BOINC 4.19 client. Same problem. CPDN runs fine and pauses fine; SETI runs fine and pauses fine; E@H runs fine, but won't pause.
I'll try kicking it out of memory at pause, as you suggest, and see what effect that has. I initially kept it in memory because that's what I've been doing with CPDN to avoid losing calculation time upon resumption.
I didn't remove it from memory after all; I found that that is a general preference and it would also remove my CPDN from memory and I need to leave that in so I don't end up repeating a lot of calculating time.
I tried resetting E@H to see if that would help, but no such luck. Following the reset, everything was going great until E@H took over again. After calculating for two hours, E@H says it's pausing and SETI begins to run, but when I check Activity Monitor, it says that E@H is still running and using half the CPU time, while SETI is using the other half. This is all on a single-CPU PowerBook G4. Here is a screen shot of Activity Monitor showing E@H continuing to run instead of pausing like it says it is.
> I didn't remove it from memory after all; I found that that is a general
> preference and it would also remove my CPDN from memory and I need to leave
> that in so I don't end up repeating a lot of calculating time.
>
> I tried resetting E@H to see if that would help, but no such luck. Following
> the reset, everything was going great until E@H took over again. After
> calculating for two hours, E@H says it's pausing and SETI begins to run, but
> when I check Activity Monitor, it says that E@H is still running and using
> half the CPU time, while SETI is using the other half. This is all on a
> single-CPU PowerBook G4. href="https://einsteinathome.org/%3Ca%20href%3D"http://mywebpages.comcast.net/freaner/Picture6.pdf">http://mywebpages.comcast.net/freaner/Picture6.pdf">Here[/url] is a screen
> shot of Activity Monitor showing E@H continuing to run instead of pausing like
> it says it is.
In your preferences, how often have you set the jobs to checkpoint? It should be frequently (at most, every few minutes).
I don't see a checkpoint in the preferences...
I set it to connect to the server once per day
and it switches between apps every 120 minutes.
I have it write to disk every 600 seconds. ( I have 1 GB RAM, and many GB of hard disk available)
C
No matter how small you set the "write to disk every xx seconds" setting, if application cannot checkpoint that often, it will not checkpoint. CPDN cannot checkpoint often, it does so in my computer for example approx every 900 seconds.
> No matter how small you set the "write to disk every xx seconds" setting, if
> application cannot checkpoint that often, it will not checkpoint. CPDN cannot
> checkpoint often, it does so in my computer for example approx every 900
> seconds.
>
> This option won't help.
I thought that if the time was set very long (say 12 hours between disk writes or checkpoints) then the BOINC code that was switching from app A to app B might wait for the next checkpoint to be completed before shutting down. But this obviously isn't the problem, if the checkpointing is every fifteen minutes.
I've finally had to detach from the E@H project. No matter what I have tried, E@H continues to say it has paused when it's supposed to switchover to another app, but never does pause. I let it run all night, just in case it might be needing some additional time for shutting down, but E@H apparently stayed active and using CPU time the whole night.
I'd really like to help with the E@H science, but I can't let the E@H client monopolize the CPU. Bruce: do you know any other Mac PowerBook users who are successfully running E@H with CPDN and SETI that I could correspond with via email to try to find a solution?
> I've finally had to detach from the E@H project. No matter what I have tried,
> E@H continues to say it has paused when it's supposed to switchover to another
> app, but never does pause. I let it run all night, just in case it might be
> needing some additional time for shutting down, but E@H apparently stayed
> active and using CPU time the whole night.
>
> I'd really like to help with the E@H science, but I can't let the E@H client
> monopolize the CPU. Bruce: do you know any other Mac PowerBook users who are
> successfully running E@H with CPDN and SETI that I could correspond with via
> email to try to find a solution?
>
> C
C, I'm going to load up SETI to run with Einstein on my G5 and watch it for a few days, to see what happens. Maybe we can figure out if it is a BOINC client issue or something being triggered by Einstein.
> > I've finally had to detach from the E@H project. No matter what I have
> tried,
> > E@H continues to say it has paused when it's supposed to switchover to
> another
> > app, but never does pause. I let it run all night, just in case it might
> be
> > needing some additional time for shutting down, but E@H apparently
> stayed
> > active and using CPU time the whole night.
> >
> > I'd really like to help with the E@H science, but I can't let the E@H
> client
> > monopolize the CPU. Bruce: do you know any other Mac PowerBook users who
> are
> > successfully running E@H with CPDN and SETI that I could correspond with
> via
> > email to try to find a solution?
> >
> > C
>
> C, I'm going to load up SETI to run with Einstein on my G5 and watch it for
> a few days, to see what happens. Maybe we can figure out if it is a BOINC
> client issue or something being triggered by Einstein.
Thank you. We'll look for any information you might provide.
I re-attached E@H and tried again. I had a SETI WU with four hours of time so far. E@H ran, and then continued to run instead of pausing when SETI came on again. The next time SETI took its turn, it restarted the WU instead of resuming where it left off. The SETI WU eventually completed and when my computer tried to upload the result, received this message:
2005-02-17 02:46:19 [SETI@home] Started upload of 01ja05aa.6435.2449.311076.158_2_0
2005-02-17 02:46:20 [SETI@home] Error on file upload: can't open log file
2005-02-17 02:46:20 [SETI@home] Error on file upload: can't open log file
ERROR: file upload returned -127
According to Paul's error list, this is probably because the log file was erased - at this point, I can only suspect that E@H had something to do with it, as it still continues to run instead of pausing, and this is the first time I've had any problems completing and returning SETI WUs. I have once again detached E@H.
> Note the words in
)
> Note the words in Parenthesis (left in memory) You can turn this off in the
> preferences. The app may still show in Activity Monitor but it should not
> show any cpu usage. If you turn off the "keep in memory" in preferences, it
> should disappear from the activity monitor when paused.
>
I agree it should not be showing CPU usage, but it does. Instead of pausing and giving 100% of the CPU usage to SETI, E&H only gives up 50% and keeps 50% for itself. This is not RAM space - it's actually incrementing CPU usage time.
Just in case the optimized Mac G4 client might be the problem, I took it out and reloaded the standard BOINC 4.19 client. Same problem. CPDN runs fine and pauses fine; SETI runs fine and pauses fine; E@H runs fine, but won't pause.
I'll try kicking it out of memory at pause, as you suggest, and see what effect that has. I initially kept it in memory because that's what I've been doing with CPDN to avoid losing calculation time upon resumption.
C
Join Team MacNN
I didn't remove it from
)
I didn't remove it from memory after all; I found that that is a general preference and it would also remove my CPDN from memory and I need to leave that in so I don't end up repeating a lot of calculating time.
I tried resetting E@H to see if that would help, but no such luck. Following the reset, everything was going great until E@H took over again. After calculating for two hours, E@H says it's pausing and SETI begins to run, but when I check Activity Monitor, it says that E@H is still running and using half the CPU time, while SETI is using the other half. This is all on a single-CPU PowerBook G4. Here is a screen shot of Activity Monitor showing E@H continuing to run instead of pausing like it says it is.
C
Join Team MacNN
> I didn't remove it from
)
> I didn't remove it from memory after all; I found that that is a general
> preference and it would also remove my CPDN from memory and I need to leave
> that in so I don't end up repeating a lot of calculating time.
>
> I tried resetting E@H to see if that would help, but no such luck. Following
> the reset, everything was going great until E@H took over again. After
> calculating for two hours, E@H says it's pausing and SETI begins to run, but
> when I check Activity Monitor, it says that E@H is still running and using
> half the CPU time, while SETI is using the other half. This is all on a
> single-CPU PowerBook G4. href="https://einsteinathome.org/%3Ca%20href%3D"http://mywebpages.comcast.net/freaner/Picture6.pdf">http://mywebpages.comcast.net/freaner/Picture6.pdf">Here[/url] is a screen
> shot of Activity Monitor showing E@H continuing to run instead of pausing like
> it says it is.
In your preferences, how often have you set the jobs to checkpoint? It should be frequently (at most, every few minutes).
Bruce
Director, Einstein@Home
I don't see a checkpoint in
)
I don't see a checkpoint in the preferences...
I set it to connect to the server once per day
and it switches between apps every 120 minutes.
I have it write to disk every 600 seconds. ( I have 1 GB RAM, and many GB of hard disk available)
C
Join Team MacNN
No matter how small you set
)
No matter how small you set the "write to disk every xx seconds" setting, if application cannot checkpoint that often, it will not checkpoint. CPDN cannot checkpoint often, it does so in my computer for example approx every 900 seconds.
This option won't help.
Administrator
Message@Home
> No matter how small you set
)
> No matter how small you set the "write to disk every xx seconds" setting, if
> application cannot checkpoint that often, it will not checkpoint. CPDN cannot
> checkpoint often, it does so in my computer for example approx every 900
> seconds.
>
> This option won't help.
I thought that if the time was set very long (say 12 hours between disk writes or checkpoints) then the BOINC code that was switching from app A to app B might wait for the next checkpoint to be completed before shutting down. But this obviously isn't the problem, if the checkpointing is every fifteen minutes.
Bruce
Director, Einstein@Home
I've finally had to detach
)
I've finally had to detach from the E@H project. No matter what I have tried, E@H continues to say it has paused when it's supposed to switchover to another app, but never does pause. I let it run all night, just in case it might be needing some additional time for shutting down, but E@H apparently stayed active and using CPU time the whole night.
I'd really like to help with the E@H science, but I can't let the E@H client monopolize the CPU. Bruce: do you know any other Mac PowerBook users who are successfully running E@H with CPDN and SETI that I could correspond with via email to try to find a solution?
C
Join Team MacNN
> I've finally had to detach
)
> I've finally had to detach from the E@H project. No matter what I have tried,
> E@H continues to say it has paused when it's supposed to switchover to another
> app, but never does pause. I let it run all night, just in case it might be
> needing some additional time for shutting down, but E@H apparently stayed
> active and using CPU time the whole night.
>
> I'd really like to help with the E@H science, but I can't let the E@H client
> monopolize the CPU. Bruce: do you know any other Mac PowerBook users who are
> successfully running E@H with CPDN and SETI that I could correspond with via
> email to try to find a solution?
>
> C
C, I'm going to load up SETI to run with Einstein on my G5 and watch it for a few days, to see what happens. Maybe we can figure out if it is a BOINC client issue or something being triggered by Einstein.
Team MacNN - The best Macintosh team ever.
> > I've finally had to
)
> > I've finally had to detach from the E@H project. No matter what I have
> tried,
> > E@H continues to say it has paused when it's supposed to switchover to
> another
> > app, but never does pause. I let it run all night, just in case it might
> be
> > needing some additional time for shutting down, but E@H apparently
> stayed
> > active and using CPU time the whole night.
> >
> > I'd really like to help with the E@H science, but I can't let the E@H
> client
> > monopolize the CPU. Bruce: do you know any other Mac PowerBook users who
> are
> > successfully running E@H with CPDN and SETI that I could correspond with
> via
> > email to try to find a solution?
> >
> > C
>
> C, I'm going to load up SETI to run with Einstein on my G5 and watch it for
> a few days, to see what happens. Maybe we can figure out if it is a BOINC
> client issue or something being triggered by Einstein.
Thank you. We'll look for any information you might provide.
Cheers,
Bruce
Director, Einstein@Home
More problems with E@H
)
More problems with E@H conflicts with SETI:
I re-attached E@H and tried again. I had a SETI WU with four hours of time so far. E@H ran, and then continued to run instead of pausing when SETI came on again. The next time SETI took its turn, it restarted the WU instead of resuming where it left off. The SETI WU eventually completed and when my computer tried to upload the result, received this message:
2005-02-17 02:46:19 [SETI@home] Started upload of 01ja05aa.6435.2449.311076.158_2_0
2005-02-17 02:46:20 [SETI@home] Error on file upload: can't open log file
2005-02-17 02:46:20 [SETI@home] Error on file upload: can't open log file
ERROR: file upload returned -127
According to Paul's error list, this is probably because the log file was erased - at this point, I can only suspect that E@H had something to do with it, as it still continues to run instead of pausing, and this is the first time I've had any problems completing and returning SETI WUs. I have once again detached E@H.
C
Join Team MacNN