RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    undo my experiement with overclocking....

    Scheduled Pinned Locked Moved Help and Support
    overclock b+overclockoverclocking
    12 Posts 5 Posters 744 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • quicksilverQ
      quicksilver @mitu
      last edited by

      @mitu so the CPU governor is reset to default each time the pi is rebooted?

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @quicksilver
        last edited by

        @quicksilver If you change it with the method posted above, yes, the sysfs modifications via echo are not persistent.

        1 Reply Last reply Reply Quote 1
        • A
          Amishgamer
          last edited by

          I'm not doubint you. But, I am wondering then why is my sysbench readings still coming in >90 seconds when they should be in the 70's.

          Any suggestions? I hate to restart building my retropie. It's finally almost the way I like it :D

          mituM 1 Reply Last reply Reply Quote 0
          • mituM
            mitu Global Moderator @Amishgamer
            last edited by

            @Amishgamer Who knows ? Do you think it matters ?

            1 Reply Last reply Reply Quote 0
            • A
              Amishgamer
              last edited by

              Well, earlier today just browsing the Emulationstation got a little choppy...

              edmaul69E 1 Reply Last reply Reply Quote 0
              • edmaul69E
                edmaul69 @Amishgamer
                last edited by edmaul69

                @Amishgamer emulationstation gets choppy if you have a bunch of systems on the pi. Turning off the help menu fixes it. Not sure if you do or not.

                1 Reply Last reply Reply Quote 0
                • EfriimE
                  Efriim @Amishgamer
                  last edited by

                  @Amishgamer
                  How do you invoke sysbench?

                  1 Reply Last reply Reply Quote 0
                  • A
                    Amishgamer
                    last edited by

                    sysbench --test=cpu --cpu-max-prime=20000 --num-threads=4 run

                    EfriimE 2 Replies Last reply Reply Quote 0
                    • EfriimE
                      Efriim @Amishgamer
                      last edited by Efriim

                      @Amishgamer
                      If i'm reading it right, pi3b+
                      my overclocked total time is 72 and 75 seconds.
                      and default gives me 81 seconds.

                      I don't know what could be adding to get >90s

                      1 Reply Last reply Reply Quote 0
                      • EfriimE
                        Efriim @Amishgamer
                        last edited by Efriim

                        @Amishgamer
                        It is likely that your pi was throttling to 1200mhz
                        setting mine to 1200mhz returned 95s sysbench.
                        while it used to do this at 70c it has been changed to 60c degrees
                        if you have a fan or heatsink make sure they are properly fixed.
                        if you only have a heatsink and no fan then this temperature is normal, and the throttling level can be increased by setting
                        temp_soft_limit=70
                        to config.txt

                        here are some commands to read from vcgencmd the current voltage and frequencies
                        for src in arm core h264 isp v3d; do echo -e "$src:\t$(vcgencmd measure_clock $src)"; done

                        for id in core sdram_p sdram_i sdram_c ; do echo -e "$id:\t$(vcgencmd measure_volts $id)"; done
                        and read the systems boot time, userspace time completion can vary by up to 5 - 90 seconds depending on the last shutdown and if the system thinks it needs a filesystem check or on usb drives.
                        systemd-analyze

                        I added them to a script to be able to execute all together

                        #!/bin/bash
                        for id in core sdram_p sdram_i sdram_c ; do echo -e "$id:\t$(vcgencmd measure_volts $id)"; done
                        for src in arm core h264 isp v3d; do echo -e "$src:\t$(vcgencmd measure_clock $src)"; done
                        cpuTemp0=$(cat /sys/class/thermal/thermal_zone0/temp)
                        cpuTemp1=$(($cpuTemp0/1000))
                        cpuTemp2=$(($cpuTemp0/100))
                        cpuTempM=$(($cpuTemp2 % $cpuTemp1))
                        echo CPU temp"="$cpuTemp1"."$cpuTempM"'C"
                        echo GPU $(/opt/vc/bin/vcgencmd measure_temp)
                        systemd-analyze
                        
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                        Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.