Alternative title: "How one line of code made our build time 100x what it should have been"
A one-line change decreased our build times by 99%
131–140 of 256 posts
Re: A one-line change decreased our build times by 99%
#132This is the most I've ever gotten out of pinterest, other than this, it's just the "wrong site that google turns up, that I can't use because it wants me to create an account just to watch the image I searched for"
Yeah i always believed it was some kind of lone evil ai that lives through search results.
The worse experience is when you have found a dead link that contains useful information that exists only as Pinterest snapshot while doing a web search...
Re: A one-line change decreased our build times by 99%
#133Seems like there's a lot of hostility towards the title, which might be considered the engineering blog equivalent of clickbait. If the authors are around, the post was quite informative and interesting to read, but I'm sure it would have been much more palatable with a more descriptive title.
But back on topic: does anyone have any insight into when git fetches things, and what it chooses to grab? It is just "when we were writing git we chose these things as being useful to have a 'please update things before running this command' implicitly run before them"? For example, git pull seems to run a fetch for you, etc.
Re: A one-line change decreased our build times by 99%
#134We recently reduced our build times by 5-10% or so by changing the default bcrypt iteration count (for tests). It also felt silly once we found it.
One thing to keep in mind is that this obviously changes the timing of your software with respect to production behaviour, which may or may not matter depending on what you are testing.
Re: A one-line change decreased our build times by 99%
#135Misleading title. They reduced their clone time by 99%. Not their build time.
With a repo that is 20GB, I can imagine that could be 99% of the build time.
Re: A one-line change decreased our build times by 99%
#136Earlier quoted context omitted.
Where does the article say "99% of the entire build was spent downloading code"?
It quotes a jenkins job going from 40 minutes to 30 seconds.
They say "Cloning our largest repo, Pinboard, went from 40 minutes to 30 seconds"
Presumably the build does more than just clone
Re: A one-line change decreased our build times by 99%
#137This is the most I've ever gotten out of pinterest, other than this, it's just the "wrong site that google turns up, that I can't use because it wants me to create an account just to watch the image I searched for"
The most frequent search keyword that I use is "-pinterest"
Yes, there seems to be no way to make it clear to Google that we want to never see certain websites in our search results. Yet, Google claims they need our information to "improve our experience".
Re: A one-line change decreased our build times by 99%
#138This is the most I've ever gotten out of pinterest, other than this, it's just the "wrong site that google turns up, that I can't use because it wants me to create an account just to watch the image I searched for"
Can we not do the thing where we pick an organization from an article and then bring up the most generic complaint you can about it in a way that is entirely irrelevant to the post? We get it, you don't like Pinterest showing up in search results, nobody does. But this has absolutely nothing to do with the article other than it being pattern matching on the word "Pinterest", which is about the least informative comme…
HN has always been very predictive.
Praise Microsoft for turning the corner, Dislike Google for ads and snooping, Praise Apple for privacy, Dislike Zoom for privacy, Dislike Pinterest for middlewaring Google Image, and so on.
Re: A one-line change decreased our build times by 99%
#139My CI servers have to build branches as well, though. A fresh clone for every build? No wonder it was slow, but even this solution seems inefficient. My preferred general solution is a persistent repository clone per build host, maintained by incremental fetch, and use git worktree add, not git clone, to checkout each build.
Re: A one-line change decreased our build times by 99%
#140Is it a common practice to clone the repo on every build (especially on web apps)? I just have Jenkins navigate to an app folder, run few git commands (hard reset, pull), and build (webpack).