GitHub’s new offer closely matches that from GitLab

Re:GitHub’s new offer closely matches that from GitLab by ddevault on Wednesday April 15, 2020 @11:31AM (#22878917)

I know I'm biased here (full disclosure: sourcehut guy here), but I really hope you'll bring that goal even lower. I recently did a comparison between GitHub, GitLab, and SourceHut on the same "worst-case" page:

https://git.sr.ht/~sircmpwn/linux/tree/master/arch/arm/boot/...

https://github.com/torvalds/linux/tree/master/arch/arm/boot/...

https://gitlab.com/ddevault/linux/-/tree/master/arch/arm/boo...

                    cold cache     warm cache
    git.sr.ht:      1.4s     72K   1.4s     48K

    github.com:     3.3s    635K   3.0s    317K*

    gitlab.com:     3.1s   1300K   1.6s     58K+

    * Hides half of the files
    + Only the initial load, it loads a bunch of stuff with JS to keep
      populating the page afterwards, and has severe performance issues
      simply using the page (on Chromium, it was straight up unusable on
      qutebrowser)

Even after the page loads, for me it's impossible to use. On a more forgiving "best-case" page, GitLab has poor performance:

https://git.sr.ht/~sircmpwn/scdoc/tree/master/src

https://github.com/ddevault/scdoc/tree/master/src

https://gitlab.com/ddevault/scdoc/-/tree/master/src

                    cold cache     warm cache
    git.sr.ht:      296ms    28K   198ms      4K

    github.com:     572ms   360K   629ms     36K

    gitlab.com:    1310ms  1311K  1110ms     16K

You should definitely make performance a core focus IMO.

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by gygitlab on Thursday April 16, 2020 @11:41AM (#22890525)

Many thanks indeed for calling this out. Performance is certainly a key goal for us and as part of the Quality group we've been increasing our performance test efforts over the last year and prioritising performance fixes with our dev teams.

We've investigated and confirmed the controller that's looks to be the cause of this and raised an Issue here - https://gitlab.com/gitlab-org/gitlab/-/issues/214681. Many thanks again.

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by emilycook on Wednesday April 15, 2020 @11:35AM (#22878964)

Oh my goodness thank you so much for this! I'm gonna show this to our performance team. I appreciate you sharing the comparison, this is very helpful.

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by ddevault on Wednesday April 15, 2020 @11:36AM (#22878997)

No problem. Good luck bringing these numbers down!

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by sytse on Wednesday April 15, 2020 @01:00PM (#22880119)

I agree, thanks for the numbers. I'll suggest to incorporate this into our Q2 OKRs.

For our references please see https://storage.googleapis.com/sitespeed-results-gitlab/gitl... and https://about.gitlab.com/handbook/engineering/performance/

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by sytse on Thursday April 16, 2020 @10:43PM (#22895734)

And we created https://gitlab.com/gitlab-org/gitlab/-/issues/214681

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by sytse on Thursday April 16, 2020 @10:55PM (#22895794)

And we quickly fixed https://gitlab.com/gitlab-org/quality/performance/-/merge_re...

[ Parent | on HN ]

Re:GitHub’s new offer closely matches that from GitLab by alrafer on Friday April 17, 2020 @02:12PM (#22901415)

Great turnaround time!

[ Parent | on HN ]