Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delay when neowofetch reaches the 'packages' line in config. #246

Closed
1 task
216598762 opened this issue Mar 19, 2024 · 2 comments
Closed
1 task

Delay when neowofetch reaches the 'packages' line in config. #246

216598762 opened this issue Mar 19, 2024 · 2 comments

Comments

@216598762
Copy link

216598762 commented Mar 19, 2024

Describe the bug

When it hits 'packages' in config, delays for about 3 seconds before completing.

  • Does this issue still occur in the master branch? No.

Expected behavior

Continuous fluid output of the lines specified in config.

Screenshots

Hang
image
Complete
image

Config

config.txt

Verbose log

neofetch.log
Ran the command recommended but replaced neofetch with neowofetch. Running neofetch alone does not produce the bug.

Additional context

Using kitty backend, zsh, and neowofetch on endeavourOS. It successfully renders my image and all other portions at expected speed.

@hykilpikonna
Copy link
Owner

I see that you have 2 packages from pipx, 7 packages from npm, 1599 packages from pacman, 15 games on steam, 5 packages on flatpak. The sequence of commands that ran to get these results are:

pipx list --short
cargo install --list
npm list -g --depth=0
pacman -Qq --color never
ls /home/null/.local/share/Steam/steamapps/common/*/
flatpak list --system
flatpak list --user

I think it's just that you have a lot of package managers and it takes time to query each of them. I tested each of them, and none seems to be particularly slow (the slowest is npm, but still finishes in 1.57s wall time), and the total wall time seems to be only 1.85s.

image

Since I can't replicate the slow down, please measure the time it takes for your machine to run each of these commands by running time {command} and we'll see which package manager is the culprit.

@hykilpikonna
Copy link
Owner

hykilpikonna commented Apr 13, 2024

Okay I optimized the npm query by not calling npm list. Should be faster now.

image

Honestly, if you are looking for speed maybe try using the fastfetch backend. Fastfetch is extremely fast compared to neofetch, but the cost is that it doesn't support a lot of package managers that we do (npm, pipx, cargo, and steam are all not supported).

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants