-
Notifications
You must be signed in to change notification settings - Fork 262
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
Generating installer too slow #92
Comments
@mzmousa That's perfectly normal as far as I am aware. My build process (including dependency installation and cloning of the repo) takes anywhere from 9 - 18 minutes |
@MarshallOfSound It is not normal and fixed in the electron-builder. Delta package is still not fixed and slow. electron-userland/electron-builder#351 |
@develar In terms of the question and this library, the times mentioned are normal I.e. Not different to the average time any user of this library would achieve. If it turns out there is an underlying issue that makes the zip process slow for all users that is a separate issue to this question. Is @paulcbetts or @kevinsawicki aware of the underlying zip issue? |
No. 5-10 minutes (includes tests) it is normal if you have heavy-weight tests (e.g. electron-builder tests — we build a lot of apps during test). Otherwise it is unacceptable time. Indicating that something is wrong in your tools/setup. Electron app on slow windows machine — Appveyor CI server — ~ 2 min 55 sec. Again — delta package is not fixed and it is very slow (4 minutes to build one delta file on OS X machine).
Yes. Decision — it is ok. |
@develar I think you are missing the point of my answer. The question was "is it normal" Definition of normal:
That time is usual, typical and expected. Hence normal....
Not much I can say to that, if there is in fact a significant speed gain to be had from fixing this issue I don't see why it can't be an open triaged issue on Squirrel.Windows for someone to tackle one day. But yeah, that's up for them to decide |
Hmmm... Why? 5-10 minutes is not expected time. Hey! My project contains 67K java files and full rebuild takes only 5 minutes. If default Squirrel.Windows pack impl tooks so much time and CPU, I have the only question, sorry.
My plan: when my changes will be stabilised, I will attempt to open another PR (#77). |
@develar I think this went off on a tangent and now we are discussing the definition of normal so I'll just end this with a TLDR TLDR: That said, as is mentioned in that PR you referenced it is virtually impossible to test the long reaching side affects of making core changed to this tool. For instance a single bugfix to handle spaces in executable names caused my app to be sent out to a few hundred users in a matter of minutes before I detected a bug due to an upgrade path from 2.0 -> 2.3 and this resulted in a bricked app (no way to update as it won't start). Testing all possible scenarios and files you would want to package is a massive task and personally I'll take the 10 minute build time and a guarantee that things will work over a 30 second build time with possible flakiness. This is why I've actually locked in our |
^^^ A Thousand Times This. I'm all for making builds fast, but not at the expense of possibly stranding users or breaking something, which is why I rejected the previous PR (not because I have like, a fetish for slow software or something) |
Closing this out as we seem to be in agreement that this is Expected(tm) |
How long should generating the installer take? My full nupkg is ~80 MB, and generating the setup.exe, and -full.nupkg files takes 5-10 minutes. Is this normal? What are ways of making this process faster?
The text was updated successfully, but these errors were encountered: