Allowing beta test apps has certainly worked to get some GPU tasks. Currently you have 4 and one has been completed and validated.
Your BOINC client is still NOT asking for CPU work. The quickest way to see if it is allowed (by preferences) to ask, is to temporarily suspend ALL CPU tasks for other projects to see if this will force a request for Einstein CPU tasks. IF that works, then you know the reason BOINC is NOT asking for CPU tasks is because it thinks other projects are more deserving. In that case you should resume all suspended tasks and let BOINC get on with its job of managing things according to your resource share settings.
The countdown clock keep resetting on them so I eventually aborted them. There were 3 or 4 of them as I recall.
There were 4 that were aborted and I think 3 of them may have been close to or even past the deadline. I wondered if you had just aborted them for that reason. I'm not sure what you mean by "countdown clock keep resetting". Could you explain what was happening? FGRP4 tasks progress in 'steps' rather than continuous increments every second. That behaviour, although quite normal, can make it look like nothing is happening.
The countdown clock I am referring to was the "remaining" column . On the tasks that would not complete the Remaining clock would countdown to a certain time value then jump back up in time. So if it had counted down to 2:00 minutes all of the sudden it would jump back to 5:00 minutes remaining. It was stuck in a loop doing that.
That happened after I updated to the latest BOINC release. (I had everything stopped when I installed the new BOINC version). After that I could not get tasks again.
I have no experience with the latest BOINC versions. All my hosts run Linux and I'm running 7.2.42 which is still the recommended version for Linux. Perhaps there are changes in how 7.6.22 works out which projects should next fetch work but that wouldn't be any sort of permanent block on Einstein. If you can get CPU tasks by the above method, then just let BOINC do its job without worrying about it.
What worries me a bit is the log entry that says "unreliable" and it points to a reliability rate of .09 > .05 - which I think is the number of task failures. Is it possible that I somehow clipped a task failure threshold. I've been running tasks for years and have completed thousands so far.
My guess is that this is of no concern to you. I don't know exactly what it means but my guess it's to do with projects that might be using very high 'reliability' to allow only one task in a quorum - ie. no 2nd task needed to validate the 'correctness' of a result. It's not used for this at Einstein and it wouldn't be the reason for not getting CPU tasks.
Thanks for that explanation
Also, on the question of CPU queue being full with Milkyway tasks. I issued a NO NEW TASKS to MilkyWay and Asteroids yesterday and the CPU queue is now down to only 8 tasks running and waiting.
If BOINC doesn't want to get Einstein at the moment, I don't think just setting NNT on other projects will work, UNLESS there is nothing else to crunch.
OK
I am thinking of reverting back to the previous BOINC version ...
I think you should persevere with the current version for a while yet.
I am
There's actually a more serious problem for you to look into. If you look at the remaining FGRP4 CPU tasks that show up on the website, you can see a huge difference between CPU time and elapsed time for all results. Such large differences are not normal. You have a quad core CPU with HT - 8 virtual cores and BOINC sees the full 8. Is your machine an iMac or a Macbook? Are you running CPU tasks on all 8? Are you monitoring CPU temperatures? Apart from BOINC stuff, are you running other CPU intensive work?
I have a IMAC with 8 virtual cores. Yes, running tasks on all 8. Yes, I monitor the temp. To keep the temp under control I restrict BOINC to 40% of CPU time. The only other tasks of significance is a weekly scan of the computer for viruses. Does the 40% limit explain the difference between elapsed time and CPU time?
UPDATE: So I am getting jobs again. Your recommendation turned the tide. I went into EAH preferences and flipped the USE CPU flag off. Jobs started flowing immediately. I flipped the USE CPU flag on again and turned off the NVIDA and INTL GPU flags and and turned-on the RUN TEST APPLICATIONS flag. I have been getting a new job whenever a EAH job completes. These are (.5 CPU + 1 AMD GPU jobs for Binary Radio Pulsar Search.
So not sure why it stopped but flipping the USE CPU flag bought it back.
Question: Does the .5 CPU indicate that I am getting only GPU jobs now? [/]
____________
Cheers,
Gary.
I've just posted a response to a similar problem in this new thread. You should read the opening post and my response and also look at a message on the BOINC boards that I linked to.
I give this advice since your recent successful entry into the Einstein GPU crunching market is likely to further reduce your chances of getting more CPU tasks here. To understand why, you need to follow the link and read it all carefully. It may be much more than you really want to digest :-).
____________
Cheers,
Gary.
Allowing beta test apps has
)
Allowing beta test apps has certainly worked to get some GPU tasks. Currently you have 4 and one has been completed and validated.
Your BOINC client is still NOT asking for CPU work. The quickest way to see if it is allowed (by preferences) to ask, is to temporarily suspend ALL CPU tasks for other projects to see if this will force a request for Einstein CPU tasks. IF that works, then you know the reason BOINC is NOT asking for CPU tasks is because it thinks other projects are more deserving. In that case you should resume all suspended tasks and let BOINC get on with its job of managing things according to your resource share settings.
The countdown clock keep resetting on them so I eventually aborted them. There were 3 or 4 of them as I recall.
There were 4 that were aborted and I think 3 of them may have been close to or even past the deadline. I wondered if you had just aborted them for that reason. I'm not sure what you mean by "countdown clock keep resetting". Could you explain what was happening? FGRP4 tasks progress in 'steps' rather than continuous increments every second. That behaviour, although quite normal, can make it look like nothing is happening.
The countdown clock I am referring to was the "remaining" column . On the tasks that would not complete the Remaining clock would countdown to a certain time value then jump back up in time. So if it had counted down to 2:00 minutes all of the sudden it would jump back to 5:00 minutes remaining. It was stuck in a loop doing that.
That happened after I updated to the latest BOINC release. (I had everything stopped when I installed the new BOINC version). After that I could not get tasks again.
I have no experience with the latest BOINC versions. All my hosts run Linux and I'm running 7.2.42 which is still the recommended version for Linux. Perhaps there are changes in how 7.6.22 works out which projects should next fetch work but that wouldn't be any sort of permanent block on Einstein. If you can get CPU tasks by the above method, then just let BOINC do its job without worrying about it.
What worries me a bit is the log entry that says "unreliable" and it points to a reliability rate of .09 > .05 - which I think is the number of task failures. Is it possible that I somehow clipped a task failure threshold. I've been running tasks for years and have completed thousands so far.
My guess is that this is of no concern to you. I don't know exactly what it means but my guess it's to do with projects that might be using very high 'reliability' to allow only one task in a quorum - ie. no 2nd task needed to validate the 'correctness' of a result. It's not used for this at Einstein and it wouldn't be the reason for not getting CPU tasks.
Thanks for that explanation
Also, on the question of CPU queue being full with Milkyway tasks. I issued a NO NEW TASKS to MilkyWay and Asteroids yesterday and the CPU queue is now down to only 8 tasks running and waiting.
If BOINC doesn't want to get Einstein at the moment, I don't think just setting NNT on other projects will work, UNLESS there is nothing else to crunch.
OK
I am thinking of reverting back to the previous BOINC version ...
I think you should persevere with the current version for a while yet.
I am
There's actually a more serious problem for you to look into. If you look at the remaining FGRP4 CPU tasks that show up on the website, you can see a huge difference between CPU time and elapsed time for all results. Such large differences are not normal. You have a quad core CPU with HT - 8 virtual cores and BOINC sees the full 8. Is your machine an iMac or a Macbook? Are you running CPU tasks on all 8? Are you monitoring CPU temperatures? Apart from BOINC stuff, are you running other CPU intensive work?
I have a IMAC with 8 virtual cores. Yes, running tasks on all 8. Yes, I monitor the temp. To keep the temp under control I restrict BOINC to 40% of CPU time. The only other tasks of significance is a weekly scan of the computer for viruses. Does the 40% limit explain the difference between elapsed time and CPU time?
UPDATE: So I am getting jobs again. Your recommendation turned the tide. I went into EAH preferences and flipped the USE CPU flag off. Jobs started flowing immediately. I flipped the USE CPU flag on again and turned off the NVIDA and INTL GPU flags and and turned-on the RUN TEST APPLICATIONS flag. I have been getting a new job whenever a EAH job completes. These are (.5 CPU + 1 AMD GPU jobs for Binary Radio Pulsar Search.
So not sure why it stopped but flipping the USE CPU flag bought it back.
Question: Does the .5 CPU indicate that I am getting only GPU jobs now? [/]
____________
Cheers,
Gary.
It's now up to 8 GPU tasks of
)
It's now up to 8 GPU tasks of which 5 have been returned.
Your RAC will be going through the roof! :-).
____________
Cheers,
Gary.
Sorry but what is my RAC? Resource Allocation perhaps??
Curtis
I've just posted a response
)
I've just posted a response to a similar problem in this new thread. You should read the opening post and my response and also look at a message on the BOINC boards that I linked to.
I give this advice since your recent successful entry into the Einstein GPU crunching market is likely to further reduce your chances of getting more CPU tasks here. To understand why, you need to follow the link and read it all carefully. It may be much more than you really want to digest :-).
____________
Cheers,
Gary.
Thanks I will look at the thread. thanks Curtis
Jasper: Thanks for your
)
Jasper:
Thanks for your insights.
I am getting GPU units again - still investigating why no cpu.
thanks
Curtis