-
Notifications
You must be signed in to change notification settings - Fork 371
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
opam list --installed is slow (depexts + yum) #4875
Comments
One easy solution is to remove from the config files the lines added by opam, which I did. So it not blocking, but with the current performance issue, these lines are too costly and thus sadly useless. |
for vim, there is some hints on ocaml-opam/opam-user-setup#53 to speed startup |
Indeed, ocaml-opam/opam-user-setup#54 should solve the slow vim startup. But I tried instructions given in ocaml-opam/opam-user-setup#53 (comment), and it did not change anything. I still find it strange that |
If you launch |
Here is the output of
Here is the debug output for
Here is the debug output for
Here is the debug output for
|
mmh, which distribution do you have? |
Fedora 33 |
BTW I observe the same behaviour with |
I believe #4791 should have fixed that. We're planning to start releasing opam 2.1.1 today (the release process is quite long so full announcement will probably be there on tuesday). Could you try the |
Tested the commits of #4792, and indeed it is much much faster, but still slow in my opinion
|
Actually |
I'll close it, feel free to reopen it, especially if you have an idea of something faster than |
As already noted in another issue, the opam command written by opam itself in the config files of the editors is slow and thus slows down the start of instances of these editors. I noted that with vim and the comment linked above noted that for emacs.
The culprit is the command
opam list --installed --short --safe --color=never [packages]
. It is rather fast (typically 0.6 s on my system) when it is given installed packages and non-existing packages (although I would expect such command to be instantaneous, not just fast, but I don't know what exactly happens under the hood and it is not blocking in practice). But it is slow when it is given at least one uninstalled package (typically 6.5 s on my system).I saw that a few issues are open related to performance regressions in latest versions. This may be related.
The text was updated successfully, but these errors were encountered: