It would be interesting to see if the setting "Use at most _% CPU time" is related to this problem. Since the app is now deprecated, it can be tested on Albert@Home only.
It would be interesting to see if the setting "Use at most _% CPU time" is related to this problem. Since the app is now deprecated, it can be tested on Albert@Home only.
Cheers
HBE
It has no impact for Boinc 7.0.42. And: We are talking about a GPU application. I'm running only one GPU task at the same time. Only BRP5 and the usage on the GTX560TI is 69% + 0,20% CPU. So i can see no reason, why this task should be suspended anyway, even if there are 5 LAT-Tasks in parallel on the CPU, which is an I7 with 8 threads. GPU can be used while the computer is used. But most of the time this computer does only crunching, nothing else.
"Leave applications in memory while suspended" is checked.
"Use at most _% CPU time" is set to 75%. Setting it to 100% CPU time doesn't fix the issue.
.......
Thanks,
Gustav
Here is the answer
Ah, ok, thanks. Gustav, just to be sure: did you perform an "update" on the client side after making the change in the web settings? This needs to be done to make the client pull the new settings from the server, only afterwards the new settings will take effect. I'm asking because in earlier BOINC versions, messages like these from your log:
I've switched back both computers from Boinc 7.0.64 to Boinc 7.0.42 and on both computers BRP5 is running successfully
This is interesting indeed. It would be really helpful if you could help us identifying the exact client version that introduced the error. If you're willing to do so, these are steps to follow:
1) Attach to our test project at http://albert.phys.uwm.edu/
2) Reproduce the error with 7.0.64
3) Reproduce no error with 7.0.42
4) Iteratively bisect the versions between those two, available here: http://boinc.berkeley.edu/dl/
By 4) I mean: given the following available versions...
4.1) pick the last working version (start with 7.0.42) and the first non-working version (start with 7.0.64)
4.2) pick the version in the middle of the set (start with 7.0.55) and test if it's working
4.3) if it's working it becomes your new "last working version". If it's failing it becomes your new "first non-working version"
4.4) continue with 4.2 until you found the failing version that introduced the error.
Please note: each test you run will reduce the versions remaining to be tested by 50%, hence will quickly tell us which client version introduced the problem (assuming that the bug was introduced in one of the version between the two you reported).
I've switched back both computers from Boinc 7.0.64 to Boinc 7.0.42 and on both computers BRP5 is running successfully
This is interesting indeed. It would be really helpful if you could help us identifying the exact client version that introduced the error. If you're willing to do so, these are steps to follow:
1) Attach to our test project at http://albert.phys.uwm.edu/
2) Reproduce the error with 7.0.64
3) Reproduce no error with 7.0.42
4) Iteratively bisect the versions between those two, available here: http://boinc.berkeley.edu/dl/
By 4) I mean: given the following available versions...
4.1) pick the last working version (start with 7.0.42) and the first non-working version (start with 7.0.64)
4.2) pick the version in the middle of the set (start with 7.0.55) and test if it's working
4.3) if it's working it becomes your new "last working version". If it's failing it becomes your new "first non-working version"
4.4) continue with 4.2 until you found the failing version that introduced the error.
Please note: each test you run will reduce the versions to be tested by 50%, hence will quickly tell us which client version introduced the problem (assuming that the bug was introduced in one of the version between the two you reported).
Thanks in advance,
Oliver
Hi Oliver,
I will perform this tests today in the evening. I have a testcomputer here, which is with Vista OS. But the problem is the same as with the two big Win7 machines. I'll keep you informed. And I will use your quicksort algorithm :-)
Hi! It would be
)
Hi!
It would be interesting to see if the setting "Use at most _% CPU time" is related to this problem. Since the app is now deprecated, it can be tested on Albert@Home only.
Cheers
HBE
RE: Hi! It would be
)
It has no impact for Boinc 7.0.42. And: We are talking about a GPU application. I'm running only one GPU task at the same time. Only BRP5 and the usage on the GTX560TI is 69% + 0,20% CPU. So i can see no reason, why this task should be suspended anyway, even if there are 5 LAT-Tasks in parallel on the CPU, which is an I7 with 8 threads. GPU can be used while the computer is used. But most of the time this computer does only crunching, nothing else.
RE: "Leave applications in
)
Here is the answer
RE: RE: "Leave
)
Ah, ok, thanks. Gustav, just to be sure: did you perform an "update" on the client side after making the change in the web settings? This needs to be done to make the client pull the new settings from the server, only afterwards the new settings will take effect. I'm asking because in earlier BOINC versions, messages like these from your log:
were related to the throttling mechanism.
Cheers
HB
RE: I've switched back
)
This is interesting indeed. It would be really helpful if you could help us identifying the exact client version that introduced the error. If you're willing to do so, these are steps to follow:
1) Attach to our test project at http://albert.phys.uwm.edu/
2) Reproduce the error with 7.0.64
3) Reproduce no error with 7.0.42
4) Iteratively bisect the versions between those two, available here: http://boinc.berkeley.edu/dl/
By 4) I mean: given the following available versions...
* 7.0.42
* 7.0.43
* 7.0.44
* 7.0.45
* 7.0.46
* 7.0.47
* 7.0.48
* 7.0.52
* 7.0.54
* 7.0.55
* 7.0.56
* 7.0.57
* 7.0.58
* 7.0.59
* 7.0.60
* 7.0.61
* 7.0.62
* 7.0.63
* 7.0.64
4.1) pick the last working version (start with 7.0.42) and the first non-working version (start with 7.0.64)
4.2) pick the version in the middle of the set (start with 7.0.55) and test if it's working
4.3) if it's working it becomes your new "last working version". If it's failing it becomes your new "first non-working version"
4.4) continue with 4.2 until you found the failing version that introduced the error.
Please note: each test you run will reduce the versions remaining to be tested by 50%, hence will quickly tell us which client version introduced the problem (assuming that the bug was introduced in one of the version between the two you reported).
Thanks in advance,
Oliver
Einstein@Home Project
RE: RE: I've switched
)
Hi Oliver,
I will perform this tests today in the evening. I have a testcomputer here, which is with Vista OS. But the problem is the same as with the two big Win7 machines. I'll keep you informed. And I will use your quicksort algorithm :-)
Great! Thank you very much!
)
Great! Thank you very much!
Einstein@Home Project
Oliver, can you pleas
)
Oliver,
can you pleas provide me a download link for all that Boinc versions. The official Boinc Download site doesn't offer them.
Regards
Here you go.
)
Here you go.
Great. Thanks
)
Great. Thanks