- C 92.3%
- Makefile 4.9%
- Assembly 2.8%
yoctofetch
REUSE status standard-readme compliant Made by Humans Packaging status Static Badge SWH
Fast and low footprint system fetch tool for the LinuxTM UAPI
In contrast to all the fetch tools out there which claim to be "really fast",
yoctofetch is an actually fast and tiny system fetch tool.
It currently has a stripped weight of about 20kb and runs in ~200μs
(yes, microseconds).
Despite its incredible performance, it still supports quite a few features:
-
Logos (guix, arch, debian and fedora)
-
The majority of common system information
-
Operating System
-
Host
-
Kernel (version)
-
Uptime
-
Shell
-
Window manager / Desktop
-
Terminal emulator
-
Memory
-
Swap
-
Battery capacity & status
-
ANSI color codes
-
-
Customization via a configuration file
-
Disable output of specific system information
-
Change colors and/or logo
-
-
NO_COLOR support
Background
I came across a multitude of sys-fetch (neofetch like) tools on the web, each one claiming to be bazingly fast. This kind of prompted me to make one which actually deserves the title blazingly fast without compromising too much on features.
Also, I like minimalistic software which has a low resource foot print and is not suspectible to all these supply chain attacks that we got on the regular nowadays.
This is why this entire thing is written as a freestanding C program, meaning the only dependency is a LinuxTM kernel to run on.
Motivation
I came across a multitude of sys-fetch (neofetch like) tools on the web, each one claiming to be bazingly fast. This kind of prompted me to make one which actually deserves the title blazingly fast without compromising too much on features.
Also, I like minimalistic software which has a low resource foot print and is not suspectible to all these supply chain attacks that we got on the regular nowadays.
This is why this entire thing is written as a freestanding C program, meaning the only dependency is a LinuxTM kernel to run on.
Freestanding environment (no libc)
This software does not depend on a libc, which means it can be linked into a tiny, static binary.
Further advantages are that it would not be affected by a bug or security hole in glibc or any other libc implementation.
However, this also limits its platform support.
Currently the following are supported:
-
Linux ABI
-
x86_64
-
aarch64
-
Source code origin
All source code has been written by humans, without the assistance of LLMs (commonly refered to as "AI").
History
This project originally started out under the name Ångströmfetch, but has been renamed since version 1.2.0.
Install
As a distro package
The Arch Linux AUR offers a stable and a git variant:
For Guix System:
guix install yoctofetchFor debian based distributions, there is a deb package available on the
Codeberg releases page.
From source
# git clone and cd to checkout
./configure
make
sudo make installInstall from repository as Guix channel
Use this repository as Guix channel with the following channel configuration/introduction:
(channel
(name 'yoctofetch)
(url "https://codeberg.org/Phosphenius/yoctofetch.git")
(branch "main")
(introduction
(make-channel-introduction
"259077c4909205af495edd5b5dded5b1173f0217"
(openpgp-fingerprint
"E504 167C B345 F93E 11AE 341C 1CDA 78BC 7F6C F294"))))The package is called yoctofetch-git:
guix install yoctofetch-gitUsage
Simply run from your shell:
yoctofetchOr put it in your .bashrc:
cd
echo "yoctofetch" >> .bashrcCustomization
The configuration file (usually ~/.config/yoctofetch/yoctofetch.conf) can be
used to en- or disable all available output options, given that configuration
file support is enabled, which is the default, but can be changed via
./configure --disable-config-file when building for some extra performance.
Per default, all options are enabled—even if there is no configuration file (support).
Performance
The actual performance depends on multiple factors, such as how yoctofetch was built and the layout of the files on the system.
Build configuration
The recommended configuration for maximum performance is something like:
./configure CC=gcc CFLAGS="-march=x86-64-v3 -O2 -flto" LDFLAGS="-Wl,--strip-all" --disable-config-fileAt this point, it is uncertain if there is any benefit to -flto. One has to
experiment with the flags a bit. On my system, this yields a binary 19K in size
which runs in < 230μs.
Also, -march=x86_64-v3 will not work on older CPUs and might have to be
replaced with -march=native or similar.
File layout
yoctofetch expects the data in files to be in a certain order or layout
and can read them faster if these expectations are met.
For the configuration file, this is usually under the control of the user and it is therefor recommended to keep the values in the configuration file in their default order.
This does not work for system files like /etc/os-release though.
So performance will vary, even on the same hardware if a different LinuxTM distro
is installed.
Benchmarks
Run with hyperfine on a laptop with AMD Ryzen 7 5825U CPU.
| Fetch | Mean (μs) | Min (μs) | Max (μs) | Relative |
|---|---|---|---|---|
yoctofetch |
217.6 ± 37.7 |
164.5 |
678.2 |
1 |
microfetch |
884.4 ± 85.8 |
645.3 |
1431.9 |
4.06 ± 0.81 |
macchina |
3100 ± 300 |
2600 |
4800 |
14.19 ± 2.77 |
uwufetch |
16800 ± 600 |
16100 |
20200 |
77.42 ± 13.75 |
fastfetch |
33400 ± 1500 |
30200 |
37400 |
153.71 ± 27.48 |
pfetch |
89100 ± 2800 |
84500 |
96400 |
409.27 ± 72.11 |
ufetch |
101200 ± 3700 |
98200 |
114500 |
464.91 ± 82.37 |
screenfetch |
243900 ± 3100 |
24000 |
25000 |
1120.85 ± 194.94 |
neofetch |
288200 ± 13800 |
270200 |
309100 |
1324.64 ± 238.35 |
Maintainers
-
Luca Kredel (luca dot kredel at web dot de)
Contributing
Open to pull requests, as long as they are written by humans and not LLMs.
See the contribution guidelines for details.
If you’ve found a bug or have a feature request, please open an issue on Codeberg.
License
All source code is provided under the terms of the GPL-3.0-or-later license.
© Luca Kredel