You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.20.1: paket install takes 40 seconds while 0.18 took 2 seconds #487
And I forgot to mention: we redefined the install process. Now it performs a selective update. This means you can edit the dependencies file or references files and "install" will try to make it work with the minimal changes in the lockfile. In order to do so it runs the resolver.
So it is expected to be a bot slower (maybe not that slow). If you just want to restore the packages, there is also the "restore" command.
That said: the first shot for this selective update is not really optimized and I will try to make it faster. Maybe we could also skip the resolver if we detect no changes. Or things like that.
14 seconds for an install isn't (IMHO) too bad considering it's doing the dependency resolution etc.. Install shouldn't be the standard command to use though - a restore should be much quicker. But if it was 2 seconds before....
Activity
forki commentedon Dec 30, 2014
The new version invalidates the cache. So the first install will create a lot more nuget traffic. Is the second install faster?
vasily-kirichenko commentedon Dec 30, 2014
No, all
installs are equally slow.forki commentedon Dec 30, 2014
Ok. That's unfortunate. I'll investigate tomorrow.
On Dec 30, 2014 3:33 PM, "Vasily Kirichenko" notifications@github.com
wrote:
forki commentedon Dec 30, 2014
Do you see this kind of performance issue also on open source project? I think I need something to run the profiler.
forki commentedon Dec 30, 2014
Also: how many projects / references files do you have?
forki commentedon Dec 30, 2014
And I forgot to mention: we redefined the install process. Now it performs a selective update. This means you can edit the dependencies file or references files and "install" will try to make it work with the minimal changes in the lockfile. In order to do so it runs the resolver.
So it is expected to be a bot slower (maybe not that slow). If you just want to restore the packages, there is also the "restore" command.
That said: the first shot for this selective update is not really optimized and I will try to make it faster. Maybe we could also skip the resolver if we detect no changes. Or things like that.
forki commentedon Dec 30, 2014
/cc @haf @agross
haf commentedon Dec 30, 2014
I've used it about 30 times today and I think it's really fast. But right now I'm only working towards the public nuget server.
isaacabraham commentedon Dec 30, 2014
If it's something to do with multiple nuget sources there's already #331 for that.
vasily-kirichenko commentedon Dec 30, 2014
36 seconds is not fast enough.
Yes, the vast majority of that time is taken by "exploring" our private nuget TeamCity server.
vasily-kirichenko commentedon Dec 30, 2014
This is our
paket.dependencies. The solution contains ~180 projects.forki commentedon Dec 30, 2014
Ok. That's sounds a bit like we broke the request caching.
On Dec 30, 2014 5:02 PM, "Vasily Kirichenko" notifications@github.com
wrote:
vasily-kirichenko commentedon Dec 30, 2014
14 seconds if I remove all the private packages. Still too slow.
isaacabraham commentedon Dec 30, 2014
14 seconds for an install isn't (IMHO) too bad considering it's doing the dependency resolution etc.. Install shouldn't be the standard command to use though - a restore should be much quicker. But if it was 2 seconds before....
forki commentedon Dec 30, 2014
Sounds like a good benchmark project ;-)
On Dec 30, 2014 5:07 PM, "Vasily Kirichenko" notifications@github.com
wrote:
8 remaining items
Put feed url into cache filename - references #487
Cache feed errors - references #487
forki commentedon Jan 1, 2015
please retry with 0.20.10
as before the second install should be a lot faster, even with multiple feeds
PERFORMANCE: Use StringBuilder for path replacement - #487
vasily-kirichenko commentedon Jan 1, 2015
32 seconds first
paket install(after updating to 0.20.11), 5 seconds subsequentinstalls.Great job!
Cache platform penalty calculation - references #487
Compute KnownTargetProfiles only once - references #487
Cache path extraction - references #487
Cache path penalty calculation - references #487
Pin sourcefile dependencies - #487
Don't enumerate all files, since we only need lib files - references #…
Relax prerelease requirements for pinned versions - references #487
forki commentedon Jan 2, 2015
should be even faster now.
Could you please retry with 0.20.21?
vasily-kirichenko commentedon Jan 2, 2015
4 seconds.