Close Menu
    X (Twitter)
    Hectic GeekHectic Geek
    • Apps
      • Apps for Mac
      • Apps for PCs
      • Best Apps
    • Concepts
      • Comparison
      • For Geeks
      • IT Careers
    • Gadgets
      • Accessories
      • Best Work Laptops
      • Budget Laptops
    • GNU/Linux
      • Ubuntu
    • How To
      • Virtualization
      • Windows
      • Windows How-To
    Hectic GeekHectic Geek
    Home » cpuburn: CPU Stress Tester for Ubuntu Linux
    Ubuntu

    cpuburn: CPU Stress Tester for Ubuntu Linux

    GayanBy GayanMarch 16, 2012Updated:January 26, 201716 Comments5 Mins Read
    Twitter Reddit Telegram WhatsApp Email
    Share
    Twitter Reddit Telegram WhatsApp Email

    If you’re a power user, then having the ability to put your CPU under a bit of stress can be quite useful. For instance, let’s say that you’ve just over clocked (running it in higher speeds than recommended, yikes!) the CPU and wanted to know if your fan or the cooling system in general could handle the new speeds (= generating more heat etc).

    Now under MS Windows OS you can find a lot of tools, however, in GNU/Linux or Ubuntu (as in this case) there aren’t that many you can use (or at least as far as I know). But, if you’re looking for a CPU stress testing utility that’s optimized for both Intel and AMD micro processors, then the utility know as “cpuburn” will come in handy.

    But please remember that, putting a lot of stress (100% of CPU usage) on your CPU (especially if you’ve over clocked it) can easily damage your hardware. So with all due respect, dear readers, if you don’t know what you’re doing, please don’t use it!. And also note that, this is not a CPU benchmark tool, but only a stress tester.

    (in the picture: I’ve used 4 terminals as I have a CPU with 4-cores, and CPU usage was measured using the awesome “Glances” system monitor).

    Main features

    *. Although it’s named “cpuburn” but in truth, it comes with few individual utilities (6 small ones) that as said are optimized for Intel and AMD CPU designs, which you can use, depending on your CPU model.

    For Intel …

    “burnP5”, “burnP6” (better than the “P5” as it supports never CPU models), “burnMMX” (also supports AMD) and “burnBX” (a CPU cache memory related test).

    For AMD …

    “burnK6”, “burnK7” and “burnMMX”.

    *. But of course you can use the AMD optimized packages in Intel chips and Intel ones in AMD etc.

    Just to make sure, I tested the AMD optimized tools with my Intel Core i3-2330 (4-cores running an 2.2GHZ. Well actually, it only has 2 cores that can deal with 4 threads simultaneously, which makes it looks like a 4-core processor in a system monitoring tool) and they did put it under full stress (100% usage).

    However, since I’m not an expert on that field, I should humbly suggest only to use the tests that are optimized for your CPU type for better results.

    Well, that’s it for the features.

    You can install “cpuburn” in Ubuntu 12.04 Precise Pangolin, 11.10 Oneiric Ocelot, 11.04 Natty Narwhal, 10.10 and 10.04 by using the below command in your Terminal window.

    sudo apt-get install cpuburn

    How to use it?

    Quite simple actually. Depending on your CPU type (Intel or AMD) choose one of the individual commands as shown above and put it in your Terminal window and press Enter!.

    An example …

    As said above, I have an Intel Core i3-2330 (4-cores) CPU and to put it under stress, I’d prefer to use the “burnP6” package (as it’s optimized for never Intel CPU from the bunch).

    So for that, I’d simply enter its command in my Terminal window as shown below.

    burnP6

    If you have multi-cores …

    This however, will only stress a single core, but to to put the whole CPU (all 4 cores) under full stress (oh come on dudes, have mercy! :P) I’ll have to open 4 terminals/tabs and enter “burnP6” under each Terminal window. So altogether, 4 “burnP6” programs will be running simultaneously. That’s it!.

    You can terminate (exit) the CPU stress utility/utilities whenever you want by pressing “Ctrl” + “c” keys. Again, if you run multiple Terminals, you’ll have to terminate each one individually.

    Update: As ‘Roy’ pointed out (in the comments) it is a bit lame to open tabs or new windows in Terminal for running multiple instances. So if you want a shortcut then you can use this other method for achieving the same task.

    Another method: Simply copy and paste the below command into your Terminal window (make sure to replace ‘burnP6’ accordingly).

    burnP6 &

    As soon as you enter this, you’ll be automatically brought back to the ‘$’ (prompt) because of the ‘&‘ argument.

    So now you can use the Terminal for executing another one while the first ‘burnP6’ is running in the background. Depending on the total of your CPU cores and their threads, calculate how many ‘burnP6’ programs are needed to run, then enter the same command accordingly (for example; if you wanted 8 threads then enter the command 8 times).

    As a shortcut (if you’re new), when you’ve executed the command at least once, you can press the up-arrow on the keyboard and the previously entered command will be pasted automatically.

    Or, you can combine all those needed running instances into a single chain command as well. For instance, if I wanted to run 4 instances of ‘burnP6’ (without having to enter one after the other) then I can use it in the below format (note there’s a space between each ‘burnP6 &‘ command).

    burnP6 & burnP6 & burnP6 & burnP6 &

    When you want to terminate them all, simply enter the below command.

    killall burnP6

    Again make sure to replace ‘burnP6’ with the command that you used. You can also kill the individual processes too but since it can complicate things, I won’t go into that here.

    You can read its manual by using the below command in your Terminal as well.

    man cpuburn

    So, if you’ve been looking for a simple yet an effective tool that can be run in Ubuntu (or GNU/Linux in general) to put your CPU under stress, then “cpuburn” is an extremely handy tool.

    However, as mentioned before, if you don’t know what you’re doing, then please don’t use it, even if you do know what you’re doing, please use it at your own risk :). Special thanks goes to “Robert Redelmeier” for creating it. Good luck.

    Share. Twitter Reddit Telegram WhatsApp Email
    Gayan

    An RHCE, 'Linux' user with 14+ years of experience. Extreme lover of Linux and FOSS. He is passionate to test every Linux distribution & compare with the previous release to write in-depth articles to help the FOSS community.

    Related Posts

    How to Check Linux CPU Usage?

    February 5, 2024

    Linux export Command: A Comprehensive Tutorial

    February 3, 2024

    Debian vs Ubuntu Server: A Brief Comparison for Beginners

    July 2, 2023

    CPU Based Simple System Stability and Benchmark Tester for Ubuntu Linux – systester

    June 16, 2023

    Typespeed: Typing Speed Testing Game for Ubuntu Linux

    March 12, 2023

    Debian vs Ubuntu in 2023- Which Linux OS is Right for You?

    January 6, 2023

    16 Comments

    1. Kasper on August 12, 2012 5:10 pm

      I recommend using psensor when doing this!

      Reply
      • Gayan on August 13, 2012 1:52 pm

        Thanks for the suggestion 'Kasper' :). 'psensor' does not work in my Dell notebook though. But it works for you, then yes, it's highly recommended. Thanks again man.

        Reply
        • Chris H. on November 19, 2015 10:44 pm

          Psensor is a Linux program & works great
          showing how quickly the temp rises!!

          Reply
          • Chris H. on November 19, 2015 10:46 pm

            The sensop showed a jump from about 43C to 50c
            in about 30 seconds! This after entering the P6 command!!

            Reply
            • Gayan on November 20, 2015 8:13 am

              🙂 .

    2. Roy on September 14, 2012 2:33 pm

      LOL open a terminal for every thread, mate? What a lack of skill!

      Reply
      • Gayan on September 14, 2012 8:43 pm

        Hey 'Roy',

        I know! :P. Seriously though, I think you're right. It's lame to do that, so I've updated the post with a better suggestion.

        Reply
    3. Matheus de Oliveira (MatheusOl) on March 6, 2013 6:50 am

      I think a good solution to avoid opening tabs on terminal and using killall to stop (as I think running it on background is “really” dangerous), you can use xargs and the -P option to run parallel process:

      NUM_CORES=`grep ‘^processor’ /proc/cpuinfo | wc -l`
      for i in {1..$NUM_CORES}; do echo burnP6; done | xargs -L 1 -P $NUM_CORES sh -c

      To stop, just press Ctrl+C.

      If you don’t want to burn all cores, you can change NUM_CORES to any value you want.

      Reply
      • Gayan on March 6, 2013 6:52 am

        Thanks ! :D.

        Reply
      • Matheus de Oliveira (MatheusOl) on March 6, 2013 6:54 am

        Ops… The second line is wrong, it should be:

        for i in `seq 1 $NUM_CORES`; do echo burnP6; done | xargs -L 1 -P $NUM_CORES sh -c

        Reply
    4. Hemant on May 29, 2013 1:37 pm

      If hyper threading is enabled than grep ‘^processor’ /proc/cpuinfo will display as many processors as the number of thread. for example if you have 2 cores each with 2 thread than the above grep command will display 4 processors.

      Reply
      • Gayan on May 29, 2013 8:36 pm

        True, but if you want to fully stress the whole CPU, then you have to put all of the cores (including the logical ones) under pressure, right ?

        Reply
    5. Volvox on July 21, 2013 4:05 pm

      Does this program validates it’s calculations? If my processor returns invalid result (because of overheating or faulty processor/memmory) will it show error?

      Reply
      • Gayan on July 21, 2013 5:08 pm

        Hi ‘Volvox’,

        I honestly don’t know, but my guess is that, it won’t.

        Reply
    6. kuldip biswas on July 6, 2014 1:00 pm

      simply great thought on linux.
      in simple you can overload your cpu by constant reboot.
      remember redhat instructions vim etc inintab dont set it to 6 or else refer man 5 inittab.
      constant reboot with hadoop or something like parallel processing or super computer hint.
      atleast i know i have to go to ininttab and reset to level 3 and write a small sh program containing
      !/bin/sh echo 0 > grep etc inittab >> replace etc initab ; init 6 or similar kind !/bin/sh reboot .
      then it will overload the cpu or more i can think like for(( i=0;i< big number ;++i)) init 6 now i have
      to calculate the factor of that big number. 1 byte=4kb then calculate that in thermal law julse
      sorry (s.m) theory.
      Now thanks to everyone. i also red this complete article. really amazing.

      Reply
    7. Bill on February 16, 2020 3:46 pm

      but burncpu has been removed from the Ubuntu repo

      Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Latest Posts

    Transforming Geek Culture with Advanced Software Development

    April 8, 2024

    The Role of Technology in Enhancing Digital Signage Solutions

    February 21, 2024

    How to Check Linux CPU Usage?

    February 5, 2024

    Linux export Command: A Comprehensive Tutorial

    February 3, 2024

    [Fixed] HDMI No Signal to TV or Monitor on Windows 10/11

    November 7, 2023

    AlmaLinux vs Ubuntu – How to Select the Best One?

    October 22, 2023

    Subscribe to Updates

    Get the latest news and updates from Hectic Geek. We won't overload you or sell your data!

    Contact
    • About Us
    • Contact Us
    • Privacy Policy
    • Write for Us
    X (Twitter)
    © 2026 Hectic Geek.

    Type above and press Enter to search. Press Esc to cancel.