fastfetch: Fastfetch is slower than Neofetch
General description of bug:
- What happened: Fastfetch is slower than Neofetch
- What should happen: Fastfetch should be faster than Neofetch
- Did it work in an older version: first time I use it
- Where did you get the binary: installed
fastfetch 2.2.3-1
with paru - Does this issue still occurs in the latest dev build? Yes
I think it’s slowing down when trying to display the shell informations.
Comparison image
Often helpful information:
The content of the configuration file you use (if any)
used the default command without any configuration
Output of env NO_CONFIG=1 fastfetch --load-config all --show-errors --stat --multithreading false --disable-linewrap false --hide-cursor false
:
$ env NO_CONFIG=1 fastfetch --load-config all --show-errors --stat --multithreading false --disable-linewrap false --hide-cursor false
-` francois@fox 0ms
.o+` ------------ 3ms
`ooo/ OS: Arch Linux x86_64 0ms
`+oooo: Host: 82FG (IdeaPad 5 15ITL05) 0ms
`+oooooo: Bios (UEFI): FHCN72WW (1.72) 0ms
-+oooooo+: Board: LNVNB161216 (SDK0J40709 WIN) 0ms
`/:-:++oooo+: Chassis: Notebook (IdeaPad 5 15ITL05) 0ms
`/++++/+++++++: Kernel: 6.6.2-arch1-1 0ms
`/++++++++++++++: Uptime: 54 mins 0ms
`/+++ooooooooooooo/` Processes: 296 1ms
./ooosssso++osssssso+` Packages: 824 (pacman) 1ms
.oossssso-````/ossssss+` Shell: bash 5.2.21 100ms
-osssssso. :ssssssso. Display (BNQ78F5): 2560x1440 @ 60Hz 478ms
:osssssss/ osssso+++. Brightness (BOE08E2): 0% 0ms
/ossssssss/ +ssssooo/- Monitor (BOE08E2): 1920x1080 px - 344x194 mm (15.55 inches, 141.68 ppi)
`/ossssso+/:- -:/+osssso+- Monitor (BNQ78F5): 2560x1440 px - 597x336 mm (26.97 inches, 108.90 ppi) 0ms
`+sso+:-` `.-/+oso: LM: login (TTY) 0ms
`++:. `-/+/ DE: No DE found 0ms
.` `/ WM: i3 (X11) 0ms
WM Theme: Unknown WM: i3 0ms
Theme: Adwaita [GTK3/4] 0ms
Icons: Papirus-Light [GTK3/4] 0ms
Font: Open Sans (12pt) [GTK3/4] 0ms
Cursor: Bibata-Modern-Classic 0ms
Wallpaper: Failed to detect the current wallpaper path 0ms
Terminal: kitty 0.31.0 0ms
Terminal Font: JetBrainsMonoNF-Regular (14pt) 126ms
Terminal Size: 150 columns x 36 rows (2550px x 1332px) 0ms
CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 (8) @ 4.70 GHz 0ms
CPU Usage: 6% 0ms
GPU: Intel Iris Xe Graphics 9ms
Memory: 4.13 GiB / 15.42 GiB (27%) 0ms
Swap: 0 B / 4.00 GiB (0%) 0ms
Disk (/): 57.55 GiB / 476.42 GiB (12%) - btrfs 0ms
Battery: 44% [Charging] 0ms
Power Adapter: Not supported on this platform 0ms
Media Player: No media found 3ms
Media: No media found 0ms
Public IP: 204ms
Local IP (wlan0): 192.168.0.13/24 * 0ms
Wifi: kot_mercier - 802.11ax (Wi-Fi 6) - WPA2 28ms
Date & Time: 2023-11-27 12:22:02 0ms
Locale: en_US.UTF-8 0ms
Vulkan: 1.3.255 - Intel open-source Mesa driver [Mesa 23.2.1-arch1.2] 13ms
OpenGL: 4.6 (Compatibility Profile) Mesa 23.2.1-arch1.2 26ms
OpenCL: clGetPlatformIDs returned 0 platforms 0ms
Users: francois - login time 2023-11-27T11:40:48+0100 0ms
Bluetooth: No bluetooth devices found 1ms
Sound: Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 1 Output (49%) 5ms
Gamepad: No devices detected 0ms
Weather: +2°C - Partly cloudy 111ms
Network IO (wlan0): 2.32 KiB/s (IN) - 1.41 KiB/s (OUT) 0ms
Disk IO (SKHynix HFS512GD9TNI): 0 B/s (R) - 0 B/s (W)
Disk IO (name): 0 B/s (R) - 0 B/s (W) 0ms
Version: fastfetch 2.2.3-84 (x86_64) 0ms
0ms
████████████████████████
████████████████████████ 0ms
Output of fastfetch --list-features
:
threads
libpci
vulkan
wayland
xcb-randr
xcb
xrandr
x11
gio
dconf
dbus
imagemagick7
chafa
zlib
xfconf
egl
glx
osmesa
opencl
libpulse
libnm
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 25 (12 by maintainers)
Commits related to this issue
- optimize(Displayserver): performance up Replace stdio with the posix api, and drop fscanf. It shows a huge performance up in my local benchmarks. About 35~40% faster per modefile than the old one. ... — committed to apocelipes/fastfetch by apocelipes 7 months ago
- Display (Linux): don't report disabled displays when using DRM Ref: #634 — committed to fastfetch-cli/fastfetch by CarterLi 7 months ago
- DisplayServer (Linux): improve performance for X11 Try fixing #634 — committed to fastfetch-cli/fastfetch by CarterLi 7 months ago
Should be fixed in the latest dev build. Please test.
On my slow linux machine,
Display
costs about 1257ms.xcb_randr_get_screen_info_reply
costs 592ms andxcb_randr_get_screen_resources_reply
costs 608ms.Thanks god KDE is deprecating X11!
I’m able to reproduce this issue. Seems that it only happens when an external display is connected and the builtin display is disabled.
It’s really strange. I will investigate it more tomorrow.
It’s expected. It’s displayserver that costs the time, which is used both for display module and lm / de module