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

wget2 2.1.0 excessive CPU usage: all cores at 100% #334

Open
mrdc opened this issue Jul 30, 2024 · 3 comments
Open

wget2 2.1.0 excessive CPU usage: all cores at 100% #334

mrdc opened this issue Jul 30, 2024 · 3 comments

Comments

@mrdc
Copy link

mrdc commented Jul 30, 2024

Hello,

I'm experiencing a bug in wget2 2.1.0: during site mirroring it occupies all cores at 100%. It's reproducible.
123

Command line I use:
wget2 --max-threads 15 -r -l 10 --reject-regex='wp-login.php?redirect_to=' --mirror --convert-links --adjust-extension --page-requisites --no-parent https://thetechnicgear.com

Tech specs:
Apple M1 Pro
macOS 14.5
wget2 installed via:
brew install wget2

wget2 --version

GNU Wget2 2.1.0 - multithreaded metalink/file/website downloader

+digest +https +ssl/gnutls +ipv6 +iri +large-file +nls -ntlm -opie +psl -hsts
+iconv +idn2 +zlib +lzma +brotlidec +zstd +bzip2 +lzip +http2 +gpgme

Hope it helps.

@rockdaboot
Copy link
Owner

Hm, here on Linux, it still shows 10% CPU usage, which is quite high.
Can you try with --progress=none and report back?

@mrdc
Copy link
Author

mrdc commented Aug 6, 2024

Hm, here on Linux, it still shows 10% CPU usage, which is quite high. Can you try with --progress=none and report back?

Now it shows 20% with the command line I've posted in the issue.
Using --progress=none drops CPU utilization to 7-12%, with some rare spikes up to 18%.

@rockdaboot
Copy link
Owner

Using --progress=none drops CPU utilization to 7-12%, with some rare spikes up to 18%.

That sounds reasonable downloads via HTTPS and also depends on the utilized network bandwidth and your CPU, of course.

I think, the progress bar issue is identified and can be fixed by limiting the number of bar updates per second. Just needs to be implemented =)

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