Replies: 7 comments 3 replies
-
ah, I think this is related to #1541 |
Beta Was this translation helpful? Give feedback.
-
that should be quite fast indeed! Do you have both files so we can benchmark them? |
Beta Was this translation helpful? Give feedback.
-
Here's a slightly slimmed-down
this now takes ~370ms, down from 1s before. Still quite a lot. It seems to roughly scale with number of packages / file size - if you comment some out then do |
Beta Was this translation helpful? Give feedback.
-
Actually I've just timed the full env, and it's closer to 2.6 seconds |
Beta Was this translation helpful? Give feedback.
-
Thanks for looking @baszalmstra . I'm on a fast machine and the pixi environment is on local SSD storage.
Here is the output with
the conda-meta folder is 41MB.
|
Beta Was this translation helpful? Give feedback.
-
There are 435 files. Here is the tail of all larger than 100kB:
|
Beta Was this translation helpful? Give feedback.
-
as well as / instead of speeding up the parsing of these files, could we avoid parsing them entirely by doing some mtime or hash check for the common case of "nothing has changed"? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As far as I understand, with
--frozen
these two commands should be very lightweight:i.e. they should "just" be verifying that the contents of
.pixi
matchpixi.lock
(and shouldn't be going out to the internet).They both take somewhere around 1 second though, which makes me wonder why. What checks do they need to do? Is there a way to make this check very fast, if neither
pixi.lock
nor the contents of.pixi
have changed? by e.g. comparing mtimes or some hash?Beta Was this translation helpful? Give feedback.
All reactions