How to Use the nproc Command to Check Your CPU Core Count in Linux

When you are compiling a massive open-source software project from source code (like a custom Linux kernel), or when you are configuring a heavily multithreaded web server, you need to know exactly how much processing power your machine has. If you tell a compiler to use 16 threads on a machine that only has 2 CPU cores, the system will become hopelessly bogged down. Conversely, if you only use 2 threads on a 16-core behemoth, you are wasting valuable resources. To instantly find out exactly how many processing units are available to your system, you should use the nproc command.

How the nproc Command Works

The nproc (number of processing units) command is a tiny, highly specialized utility built into almost every Linux distribution. Its entire purpose is to query the system hardware and output a single integer representing the total number of logical CPU cores available to your current environment.

Basic Usage

To check your CPU core count, simply type the command into your terminal and press Enter.

nproc

The output will be a single number on the next line. For example, if you are running a modern quad-core processor with hyperthreading (which splits each physical core into two logical threads), the output will be:

8

This tells you that your system can handle 8 concurrent processing threads optimally.

Using nproc in Scripts and Workflows

Because the command outputs a clean, bare integer without any formatting or extra text, it is incredibly useful for automating shell scripts or passing variables to other commands.

For example, if you are using the make command to compile software, you can use the -j (jobs) flag to specify how many CPU cores the compiler should use. Instead of hardcoding the number 8, you can use a bash subshell to dynamically inject the result of the nproc command:

make -j$(nproc)

This is highly recommended for developers who write scripts that will be distributed to other people. By using $(nproc), the compilation script will automatically scale to use 100% of the available CPU power, regardless of whether the script is run on a tiny 2-core Raspberry Pi or a massive 64-core enterprise database server.