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
choco search super slow compared to website #1740
Comments
Howdy @esamo - thanks for the kudos!
As far as update - The second item is called Package Indexing - something we have on our roadmap. We are quite familiar with other platforms and package indexes have been on my list for a few years. I'm going to put this into _Triaging, and we'll visit back to see if you determined what the network issue was along the route for choco search. |
Actually, are you calling |
Ok so my env is: IPv4 Looks to me this is about data size. It's faster on a better connection. These are just lines of text though, so I'm confused. I did some testing. Why 210 package names (12 kB of text) are using 13 Mb/s for about 1s or 5Mb/s for 4s? |
@esamo upgrade to Chocolatey 0.10.13 and see if that improves your results. |
Hi there!
Nice job on the tool, much appreciated!
I can't leave it though without saying that
cmd.exe choco search
works super slow compared to searching on the websitehttps://chocolatey.org/packages
.It should be faster as it does not involve browser, images and a lot of stuff, hence I don't understand at all why is this so slow.
It takes 8 seconds to fetch packages by query
google
in command line and it takes almost no time at all on the website, it's uncomparable.Another thing is that all the packages could be downloaded with
update
command exactly like it happens in linux package manager and then search is performed on locally stored index.Chocolatey v0.10.11
Windows 10 x64
The text was updated successfully, but these errors were encountered: