-
Notifications
You must be signed in to change notification settings - Fork 365
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 2.1] opam list --installed is really slow #4916
Comments
What is you distro? Can you share the |
for vim, you can find in this issue ocaml-opam/opam-user-setup#53 other way to speedup loading. |
Sorry, I completely missed #4875 .
|
pacman shouldn't take so much time to query for depexts. Can you launch |
I'm using openSUSE Tumbleweed and opam 2.1.1 and ran into the same issue. Interestingly, loading the opam files from repo default takes about 7s but deleting this folder also takes 1.5s which seems weird to me (or some long operation after deletion is missing a timestamp). opam config report
opam list --installed --debug
|
related to #4586 |
Same issue for the startup time in Emacs, narrowed down to a call to |
With
opam 2.0.9
, consistently below 100ms :With
opam 2.1.0
, around 10s on first query and then around 500ms:The same behaviour can be observed with
opam 2.1.1
(and when building currentmaster
).I had some trouble bisecting the issue, due to incompatible dune versions. I can take additional time for this if needed.
I stumbled onto this issue due to what is inserted by
opam-user-setup
in~/.vimrc
, leading tovim
starting quite slowly.Thank you very much for
opam
!Addendum: While trying to reproduce this issue, I have found #4311. Thus, I search for https://github.com/ocaml-opam/opam-rt and was wondering: would it be reasonable to add performance regression tests for such issues? With respect to the CI machine potentially changing, etc, it seemed non-trivial to me to have reliable CI about this. I am interested in possible hints about this, and can create another issue on the opam-rt repo if this is off-topic here. Thank you again!
The text was updated successfully, but these errors were encountered: