Posts by MeasurementRick

1) Questions and Answers : Unix/Linux : Overclocking on Raspberry Pi 4 (Message 99693) Posted 16 Nov 2020 by MeasurementRick Post: Thanks for the info, that gives me a much better picture of how things work with Rosetta.
2) Message boards : Number crunching : Rosetta running on ARM platforms (Message 99330) Posted 14 Oct 2020 by MeasurementRick Post: As a heads up to the (more adventurous) Raspberry Pi folks on this thread, there is a 64-bit RPiOS beta. It came out in late May and has been updated numerous times since the initial release: https://www.raspberrypi.org/forums/viewtopic.php?p=1668160 I have the 64-bit RPiOS running on three Pi boards. All of them are v4 boards (Model B), two with 4GB of RAM and one with 8GB of RAM. I've had this setup running since early Sept and R@H has been working fine that whole time, no issues at all. Not sure what the estimate is on when the GA version of the 64-bit OS will be ready.
3) Questions and Answers : Preferences : CPU Time For Tasks (Message 98786) Posted 7 Sep 2020 by MeasurementRick Post: Thanks for answers, I appreciate the insights.
4) Questions and Answers : Unix/Linux : Overclocking on Raspberry Pi 4 (Message 98763) Posted 6 Sep 2020 by MeasurementRick Post: I've got BOINC running R@h on a Raspberry Pi 4, the newest board w/ 8GB of RAM. I decided to overclock the Pi CPU so I updated /boot/config.txt: over_voltage=6 arm_freq=2000 In other words: I took the CPU clock speed up from the default of 1.5 GHz to 2.0 GHz. It's been running on this config for several days, no issues with under-voltage: $ vcgencmd get_throttled throttled=0x0 While everything is running fine I haven't noticed any meaningful improvement in R@h tasks completion times. Before the overclock my tasks were completing in ~28,800s (i.e., 8 hours). After the overclock completion times are pretty much exactly the same, albeit I occasionally see tasks finish up in just under 28,000s (i.e., 7:45 hours). So despite a 33% boost in clock speed for the CPU I'm not seeing any meaningful improvement in R@h performance. My questions are: 1) Is there anything else I need to do with either R@h setting or BOINC settings to recognize this increased CPU clock speed? 2) Or is R@h sending bigger WUs to this machine that fit within a ~8 hour processing window? I have not modified the "Target CPU run time" setting from the default of 8 hours. I'd assume if this were the case I'd be seeing higher daily point totals, but that doesn't seem to be happening. Thanks in advance.
5) Questions and Answers : Preferences : CPU Time For Tasks (Message 98762) Posted 6 Sep 2020 by MeasurementRick Post: Thanks for this info. So for a machine running R@h 24/7 are there any pros & cons for changing from the "Target CPU run time" default of 8 hours? - for example, dropping it to 6 hours. - for example, upping it to 10 hours. I'm trying to understand how this setting works in practice. 1) Are different types of tasks downloaded? 2) Are there changes to the amount of points awarded? 3) Any benefit to the R&h project? (i.e., they need more people to take on 10-12 hour tasks.) Thanks in advance.