Well a bit later and I've upgraded it from Jessie-Lite to Stretch and it seems to be working now. Its still using the in-place at the moment.
I did check the app_info and it was overwritten when I unpacked the in-place (over the top of out-of-place). The files had the correct owner (boinc) and execute permission for the binary. I will let it crunch for a bit and see how it goes. In-place memory goes from 112Mb to 122Mb before dropping back.
The Pi locks up after a minute or two. The SSH session times out. I have to power it off and on again to get it going. No messages in BOINC logs apart from starting task, etc. It seems to run okay under Stretch though so maybe it depends on something that Stretch has updated. Stretch is the testing release of Debian, Jessie is the current release. I expect the slower times I am seeing since the 3rd of September are something in the Stretch release using more CPU than before. My other Pi's are also running Stretch so it's consistent with Stretch updates causing a slow-down. The others are running the project supplied beta app.
The Pi locks up after a minute or two. The SSH session times out. I have to power it off and on again to get it going. No messages in BOINC logs apart from starting task, etc. It seems to run okay under Stretch though so maybe it depends on something that Stretch has updated. Stretch is the testing release of Debian, Jessie is the current release. I expect the slower times I am seeing since the 3rd of September are something in the Stretch release using more CPU than before. My other Pi's are also running Stretch so it's consistent with Stretch updates causing a slow-down. The others are running the project supplied beta app.
Consider running Ubuntu Mate on one Pi3 just to see if it fixes the problems you seeing. If it does then you can decide how to proceed.
One thought, what version GCC did you use to compile it? Jessie-Lite seems to have "gcc version 4.9.2 (Raspbian 4.9.2-10)". The Stretch release is up to 6.1. I am wondering if you need to compile it on Jessie-Lite (ie probably an older GCC than you used).
The app starts and they start using up the memory and the percentage complete starts to increment before the Pi crashes.
One thought, what version GCC did you use to compile it? Jessie-Lite seems to have "gcc version 4.9.2 (Raspbian 4.9.2-10)". The Stretch release is up to 6.1. I am wondering if you need to compile it on Jessie-Lite (ie probably an older GCC than you used).
The app starts and they start using up the memory and the percentage complete starts to increment before the Pi crashes.
I have used gcc 5.4.0 for the final Version. I've compiled it with 4.9.3; 5.4.0 and 6.1.0. After benching all of these, I've decided to go with gcc-5.3.0. It gave me the fastest App.
I think the used gcc-version isn't related to your problem. I've also used stretching for compile it. I don't have a idea what can cause such a "device-freeze/crash-issues".In nearly all cases you should get a "Error while Computing".
I'm afraid about this. It can be somethink hardware related. I know this kind of Problem when I OC'ed my device too far. It starts crunching and after some minutes the PI freezes.
e.g.: I can overclock my Odroid-C2 to 1.75Ghz using the normal BRP-App. Using the optimized-App it starts to crunch but after some seconds/minutes it freezes. I can only get 1.68Ghz stable using the optimized Version.
The optimized App does the same work in nearly the half time... the PI need's more current and produces more heat, than using the normal Version.
The only thing I can imagine is a heat-issues. And maybe that can explain the runtime-Problems on your other devices too.
1. Do you use a Heatsink/Fan?
2. What are your temperatures when running the BRP-App (normal/optimized)
3. can you do a stress-test using CPUburn-A53 or somethink else? (even this produces lessheat than the out-of-place, on my overclocked RPI3!!!)
I will try do a fresh clean installation of Raspbian-Jessie on my PI3 and try to readjust your problem. Hopefully I'm getting the same Issues. But I can do it tomorrow, I'm at work by now. No time at the moment, Sorry :/
as I have promised here are a BRP-App compiled for the RPI3. Due to the limited RAM of the RPI3 I've made two Versions. You could select that one that fits your needs.
Notes:
This Version is not only restricted to the Raspberry PI 3 it may run on other Devices with a Cortex-A53, but it is highly optimized for the Raspberry Pi 3.
If running a other Cortex-A53-device that has 64bit(AARCH64)-support you should consider using this Version for best performace.
as I have promised here are a BRP-App compiled for the RPI3. Due to the limited RAM of the RPI3 I've made two Versions. You could select that one that fits your needs.
Notes:
This Version is not only restricted to the Raspberry PI 3 it may run on other Devices with a Cortex-A53, but it is highly optimized for the Raspberry Pi 3.
If running a other Cortex-A53-device that has 64bit(AARCH64)-support you should consider using this Version for best performace.
Great, I will try it out!
Would be great if you tell us wich device you are using auf how the app perform's.
Reimaged the problem Pi3 with Jessie-Lite and am back to running the beta 1.47 app. Its looking like it will do them in 42k seconds which I was getting before the 3rd of September. That would confirm my suspicion that Stretch introduced something that slows the Pi down quite a lot.
The Pi3 has a heatsink, no case and has a desk fan pointed at it. Heatsink doesn't feel as hot as the other Pi's (that have cases). Its running at stock speed. I can try another Pi3 and see how it goes.
Reimaged the problem Pi3 with Jessie-Lite and am back to running the beta 1.47 app. Its looking like it will do them in 42k seconds which I was getting before the 3rd of September. That would confirm my suspicion that Stretch introduced something that slows the Pi down quite a lot.
The Pi3 has a heatsink, no case and has a desk fan pointed at it. Heatsink doesn't feel as hot as the other Pi's (that have cases). Its running at stock speed. I can try another Pi3 and see how it goes.
what temps are your Piz running at? one with fan others without ---> cat /sys/class/thermal/thermal_zone0/temp
42k seems about right. This is what mine run at but 63k which you reported earlier seems a bit high. are you doing anything else on these nodes?
Well a bit later and I've
)
Well a bit later and I've upgraded it from Jessie-Lite to Stretch and it seems to be working now. Its still using the in-place at the moment.
I did check the app_info and it was overwritten when I unpacked the in-place (over the top of out-of-place). The files had the correct owner (boinc) and execute permission for the binary. I will let it crunch for a bit and see how it goes. In-place memory goes from 112Mb to 122Mb before dropping back.
MarksRpiCluster
Hello Porkypies,sry for the
)
Hello Porkypies,
sry for the trouble, not shure what causes that...
What means "crashed the Pi" is it freezing or restarting? Or do you get simply a "Error while Computing"?
A little bounce of the RAM-usage is normal for the inplace. It seems to be a little bug but not a big deal at all.
The Pi locks up after a
)
The Pi locks up after a minute or two. The SSH session times out. I have to power it off and on again to get it going. No messages in BOINC logs apart from starting task, etc. It seems to run okay under Stretch though so maybe it depends on something that Stretch has updated. Stretch is the testing release of Debian, Jessie is the current release. I expect the slower times I am seeing since the 3rd of September are something in the Stretch release using more CPU than before. My other Pi's are also running Stretch so it's consistent with Stretch updates causing a slow-down. The others are running the project supplied beta app.
MarksRpiCluster
PorkyPies wrote:The Pi locks
)
Consider running Ubuntu Mate on one Pi3 just to see if it fixes the problems you seeing. If it does then you can decide how to proceed.
One thought, what version GCC
)
One thought, what version GCC did you use to compile it? Jessie-Lite seems to have "gcc version 4.9.2 (Raspbian 4.9.2-10)". The Stretch release is up to 6.1. I am wondering if you need to compile it on Jessie-Lite (ie probably an older GCC than you used).
The app starts and they start using up the memory and the percentage complete starts to increment before the Pi crashes.
MarksRpiCluster
PorkyPies wrote:One thought,
)
I have used gcc 5.4.0 for the final Version. I've compiled it with 4.9.3; 5.4.0 and 6.1.0. After benching all of these, I've decided to go with gcc-5.3.0. It gave me the fastest App.
I think the used gcc-version isn't related to your problem. I've also used stretching for compile it. I don't have a idea what can cause such a "device-freeze/crash-issues".In nearly all cases you should get a "Error while Computing".
I'm afraid about this. It can be somethink hardware related. I know this kind of Problem when I OC'ed my device too far. It starts crunching and after some minutes the PI freezes.
e.g.: I can overclock my Odroid-C2 to 1.75Ghz using the normal BRP-App. Using the optimized-App it starts to crunch but after some seconds/minutes it freezes. I can only get 1.68Ghz stable using the optimized Version.
The optimized App does the same work in nearly the half time... the PI need's more current and produces more heat, than using the normal Version.
The only thing I can imagine is a heat-issues. And maybe that can explain the runtime-Problems on your other devices too.
1. Do you use a Heatsink/Fan?
2. What are your temperatures when running the BRP-App (normal/optimized)
3. can you do a stress-test using CPUburn-A53 or somethink else? (even this produces less heat than the out-of-place, on my overclocked RPI3!!!)
I will try do a fresh clean installation of Raspbian-Jessie on my PI3 and try to readjust your problem. Hopefully I'm getting the same Issues. But I can do it tomorrow, I'm at work by now. No time at the moment, Sorry :/
N30dG wrote:Hello,as I have
)
Great, I will try it out!
BQL_FFM wrote:N30dG
)
Would be great if you tell us wich device you are using auf how the app perform's.
Reimaged the problem Pi3 with
)
Reimaged the problem Pi3 with Jessie-Lite and am back to running the beta 1.47 app. Its looking like it will do them in 42k seconds which I was getting before the 3rd of September. That would confirm my suspicion that Stretch introduced something that slows the Pi down quite a lot.
The Pi3 has a heatsink, no case and has a desk fan pointed at it. Heatsink doesn't feel as hot as the other Pi's (that have cases). Its running at stock speed. I can try another Pi3 and see how it goes.
MarksRpiCluster
PorkyPies wrote:Reimaged the
)
what temps are your Piz running at? one with fan others without ---> cat /sys/class/thermal/thermal_zone0/temp
42k seems about right. This is what mine run at but 63k which you reported earlier seems a bit high. are you doing anything else on these nodes?