This is a multi-part blog looking at a DreamQuest N95 Mini PC running Linux. The model we’re testing has an Intel N95 processor, 32GB of DDR4 RAM, and a 1TB M.2 SSD. It sounds like an inexpensive machine to run Linux.
This article benchmarks the DreamQuest N95 Mini PC. The tests are run using the Phoronix Test Suite unless otherwise stated. Rather than compare the DreamQuest’s performance against processors found in modern mini PCs, we’re going to take a different approach here.
We benchmark the machine against a server/workstation, a tiny desktop PC, and a fairly old mini PC. We want to see how well the DreamQuest Mini PC might function say as a home server or as a desktop replacement.

Each machine is tested with the same software and configured to ensure consistency between results. All power management functionality is disabled when running the benchmarks. For ease of reference, the system’s specifications are listed on the final page together with links to all articles in this series.
Let’s start with some general system tests.

$ phoronix-test-suite benchmark build-linux-kernel
The benchmark show how long it takes to build the Linux 6.8 kernel in a default configuration. The test uses all cores/threads of a PC, but it’s not the type of test where CPU cores run at 100%. A lot of the time, the compiler is waiting on other things like RAM and disk. It’s therefore a good indicator of the general system performance of a machine.
The DreamQuest N95 puts in an admirable performance given that its CPU is a mere 15W TDP whereas the Xeon and HP i5-6500T machines are 105W TDP and 35W TDP respectively. The N95 runs the HP fairly close. Naturally, the Xeon machine compiles the kernel quicker courtesy of its much higher number of cores (12 cores 24 threads).

$ phoronix-test-suite benchmark encode-flac
The DreamQuest machine again runs the HP machine fairly close, and trashes the Xeon into the bargain. The benchmark only uses a single core. The Xeon is even beaten comfortably by the i3-5005U Mini PC which highlights the deficiencies of the Xeon CPU with software running on a single core.
This benchmark indicates that the DreamQuest machine will make a good home server or as a desktop machine given that for most of the time its 4 cores will not be maxed out.
Next page: Page 2 – Processor
Pages in this article:Page 1 – Introduction / SystemPage 2 – ProcessorPage 3 – Memory / GraphicsPage 4 – Disk / WiFiPage 5 – Specifications

Complete list of articles in this series:

DreamQuest N95 Mini PC

Part 1Introduction to the series with an interrogation of the system

Part 2Benchmarking the DreamQuest N95 Mini PC

1.7K
Finding the largest directories in a Linux system is like playing detective in a world of data. It’s not just about freeing up disk space—it’s about understanding where your resources are being used and making informed decisions about what to keep, what to archive, and what to delete.
In this blog, I’ll walk you through various ways to unearth the heavyweight directories lurking in your Linux system. Let’s dive in, and yes, we’ll sprinkle a bit of my personal spice along the way.
The du command: The traditional heavyweight
The du (disk usage) command is the old reliable of finding out how much space a directory is using. It’s like that old detective coat you can’t part with—never fails you. Here’s how to use it:
Basic usage
du -sh /path/to/directory

The -s option gives you a summary instead of listing every file, and -h makes the output human-readable (who really counts bytes these days?).
Finding the top offenders
But what if we want to find the largest directories within a certain path? Enter the sorting magic:
du -h /path/to/directory | sort -rh | head -n 10

This command will list the top 10 heavyweight directories in descending order. The sort command is our friend here, with -r reversing the order (because we want the largest, not the smallest) and -h handling human-readable numbers (yes, it knows that 1M is larger than 1K).
Output
1.5G /path/to/directory/subdir1
1.2G /path/to/directory/subdir2
800M /path/to/directory/subdir3
…

Ah, the satisfaction of seeing exactly where your disk space has gone. Priceless. Let me give you a practical example. To list the sizes of directories in the current working directory and sort them to find the largest, you can use the following command:
du -h –max-depth=1 | sort -rh | head -n 5
Example:
1.5G ./dir1
1.2G ./dir2
800M ./dir3
600M ./dir4
450M ./dir5
The graphical approach: For the visually inclined
Not everyone loves the terminal (though I can’t imagine why). For those who prefer a graphical interface, there’s Baobab, the Disk Usage Analyzer in Ubuntu.
baobab command usage in linux

Simply open it from your applications menu, and you’ll be presented with a visual breakdown of your disk usage. It’s like a map to treasure, but instead of treasure, it’s data you probably forgot about.
While I personally prefer the terminal (there’s something about text output that just feels more like hacking), I can’t deny the appeal of seeing your data usage laid out in colorful graphs.
The ncdu command: A modern twist
For those who want a bit of both worlds—terminal-based but with an easy-to-navigate interface—ncdu (NCurses Disk Usage) is the answer. It’s like du went to the gym and came back with a new UI.
Installation steps:
Debian/Ubuntu and derivatives
sudo apt-get update
sudo apt-get install ncdu

Fedora
sudo dnf update
sudo dnf install ncdu

CentOS/RHEL
For CentOS or RHEL 7 and below, you might need the EPEL repository:
sudo yum install epel-release
sudo yum update
sudo yum install ncdu

For CentOS/RHEL 8 and newer versions, use dnf instead:

sudo dnf install epel-release
sudo dnf update
sudo dnf install ncdu

Arch Linux
sudo pacman -Syu
sudo pacman -S ncdu

openSUSE
sudo zypper refresh
sudo zypper install ncdu

Alpine Linux
sudo apk add ncdu

Gentoo
sudo emerge –update –newuse ncdu
And run it with:
ncdu /path/to/directory

You’ll be greeted with a navigable interface showing your directories, their sizes, and you can even delete files from within ncdu. Be careful, though; with great power comes great responsibility.
Example:

FAQ: Finding the largest directories in Linux
Can I use the du command on the entire system?
Yes, you can, but be prepared to wait because it’ll take some time. Use du -sh / to see the total disk usage of your root directory, but remember, this scans everything, so it might take a while.

How can I exclude a specific directory when using du?
If you want to exclude a directory, you can use the –exclude flag. For example, du -sh –exclude=/path/to/exclude /path/to/directory will calculate the size of /path/to/directory without including the specified excluded path.
Is ncdu better than du?
“Better” is subjective. ncdu offers a more user-friendly interface and interactive usage, making it easier for some users to navigate and manage files directly. du, on the other hand, is straightforward and perfect for quick, scriptable commands. Your preference will depend on your needs and how you like to work.
Can Baobab scan network locations?
Yes, Baobab can scan network locations, but the performance and accuracy can depend on the network’s stability and the remote file system’s characteristics. Use File > Connect to Server in Baobab to add a network location.
What does the sort -rh command do?
The sort -rh command sorts the output in human-readable format (-h, where 1K is less than 1M) and in reverse order (-r), ensuring that larger sizes appear at the top of the list.
How do I install ncdu if it’s not available on my system?
If ncdu is not already installed, you can install it using your distribution’s package manager. For Ubuntu or Debian-based systems, the command is sudo apt-get install ncdu. For Red Hat-based systems, use sudo yum install ncdu.

Can I find the largest files instead of directories?
Absolutely. While the methods mentioned focus on directories, you can find large files using the find command. For example, find /path/to/search -type f -exec du -h {} + | sort -rh | head -n 10 will list the top 10 largest files in the specified path.
How can I monitor disk usage over time?
To monitor disk usage over time, you might need to use additional tools or scripts. One simple approach is to run a du command periodically (via cron jobs, for example) and save the output to a file for later analysis. There are also more sophisticated monitoring solutions available that can track disk usage trends.
Conclusion
There are many ways to find the largest directories in your Linux system, each with its own charm. I personally lean towards ncdu for its balance of power and usability, but I’ve been known to run a quick du command just for the nostalgia.
So, go ahead, play detective with your file system. You might be surprised at what you find hiding in the depths of your directories.