Comment by ddevault

6 years ago

About 18K git & hg repositories, for about 13.5K users. We also run about 5,000 CI jobs per week, including for some large projects like Nim and Zig, Neovim, OpenSMTPD, etc. We have 10 dedicated servers at the moment. And I didn't throw an open source solution on these servers - I built these open source services from the ground up.

6 comments

ddevault

Reply
bdcravens  6 years ago

So you're comparing your scalability with a company with over 40m users and 100m repos.

Can you talk about the geographic distribution of your 10 servers?

  • ddevault  6 years ago

    I would like to remind you of my earlier point:

    SourceHut is not the same scale as GitHub. This does not change the fact that SourceHut is faster and more reliable. We have an advantage - fewer users and repos - but still, that doesn't change the fact that we're faster and more reliable.

    This has been objectively demonstrated as a numerical fact:

    https://forgeperf.org

    And yes, 9 of those servers are in Philadelphia (the other is in San Franscisco, but it's for backups, not distribution). That doesn't change the fact that, despite being more distant from many users, our pages load faster. In this respect, we have a disadvantage from GitHub, but we're still faster.

    GitHub and Sourcehut are working at different scales. That doesn't change the fact that SourceHut is faster.

    • bdcravens  6 years ago

      I was considering your claim:

      > we use a distributed architecture

      > SourceHut is faster

      I wasn't questioning that some of the web features are fast. I'm sure when Github was 10 servers their pages were fast too. I suspect if I threw Gitlab on a 9-server cluster on AWS they'd also be quick.

      1 reply →

    • fortuity  6 years ago

      > This has been objectively demonstrated as a numerical fact:

      While your tests are indeed objective, I don't think they're very useful. For example, why does your performance test ignore caching?

      GitHub's summary page loads 27KiB of data for me unauthenticated, which is about 6% of the 452KiB you're displaying in your first table. The vast majority of developers who browse GitHub will not be loading 452KiB of static assets every single page load.

      Anecdotally, GitHub's "pjax" navigation feels about as fast as SourceHut on my aging hardware.

      1 reply →