undefined | Better HN

0 pointsmerb7y ago0 comments

Loading a Merge Request with 168 changes, basically breaks a 4cpu's 4gb instance on gitlab, so yes, "the most basic areas of the core product is almost unusable".

And while some integration is good... A lot of recent stuff is just "we try to grab the easy money"

0 comments

sytse7y ago

Yep, load times of large merge requests was a big problem. In 11.1 we launched a refactor of merge requests to solve this https://about.gitlab.com/2018/07/22/gitlab-11-1-released/#me...

That got the time down for the worst case we measure from 15 seconds to 3 seconds, see https://news.ycombinator.com/item?id=17671300

merbOP7y ago

we are on 11.1 and it takes way more than 3 seconds (or even 15 seconds) (Request takes around 7 seconds and parsing it, and parsing it takes 10 seconds).

(P.S.: I also have the same source in gitea of a way less powerful instance which basically renders the whole thing in way less than 1 second.)

j / k navigate · click thread line to collapse