-
Notifications
You must be signed in to change notification settings - Fork 525
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
over an hour for paket update
#607
Comments
Wow that's really bad perf. I wonder why CPU is used at all. Usually bad Regarding "exploring". It basically means that we have to look at the next
|
I cloned this repo and did a couple of performance wizard runs on it. The first one for CPU usage. Being that performance gets slower as it goes when I run it, it feels like a memory issues. I ran the memory performance wizard too, but the analysis process is taking a while to churn through an 8 GB log file. I'll report back when I get it. |
The memory performance wizard brings up the same code. cpu .vspx 9 MB |
I was trying to install xunit 2 with https://github.com/ctaggart/Paket09x/tree/collections
|
After a quick look I think there are two things that produce this strange
|
Why are all the
May be |
As I wrote above it's detecting a conflict between prerelease requirement
|
Quick question in order to tackle part 2) of this. What profiler tools do you use? |
Could look at the use of nessos stream library, which has some large performance gains over seq operations. Not sure about set though. From: Cameron Taggartmailto:notifications@github.com The memory performance wizard brings up the same code. cpu .vspx 9 MB Reply to this email directly or view it on GitHub: |
Ok I released a hotfix which should relax the prerelease requirements. Please check if this works for you. I will still keep this issue open since I really want to analyze the memory issue. |
Regarding streams: I started with lists, then went over to sets since I needed uniqueness. Then I changed the order in the set. So in the I think we need a priority queue for the open dependencies and a set for the closed dependencies. |
Yeah - I am thinking more "streams rather than lots of chained Seq. operations" than replacements for Set operations. |
I used the profiler that comes with Visual Studio 2013 Ultimate. Select |
it looks like we are no longer tail recursive. I will try to fix that. Did the quickfix help? |
Yes, thank you! |
closing this, but I'm still refactoring the code |
paket
has been churning away on anupdate
for over an hour now and is not complete. It has been hovering at about 26% CPU. Theexploring
lines are slowly being printed by the minute. What can be done to improve performance?We have 44 dependenies listed in
paket.dependencies
along with two sources:Current output:
What does
exploring
mean? Why are so many versioned explored?The text was updated successfully, but these errors were encountered: