4 ms·

I've ported a couple of repos to CodeFloe in the last few days, and so far, so good. Performance is similar to when I self-host Forgejo on a dedicated VPS where

by mtlynch 1mo ago

I've ported a couple of repos to CodeFloe in the last few days, and so far, so good. Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast. And their built-in CI is pretty nice. It's a huge contrast to Codeberg, which struggles with basic navigation of the web UI and every git push or pull takes 2-10s.

jorams 1mo ago
> Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast. I don't mean to be negative, but that's probably because it's pretty much the same thing. Codefloe is tiny. Some quick counting shows it has a grand total of 1012 registered users, including bots, and 1416 public repositories of which the top 3 with the most stars (I know this is a mostly meaningless metric, but for scale) have 27, 13, and 8. It's too small to run into scaling issues.
- rererereferred 1mo ago
  They keep public records updated quarterly (neat!). Until June they had 774 users and 2090 repos: https://codefloe.com/codefloe/analytics/src/branch/main/reports/2026-Q2/quarterly_report.md https://codefloe.com/codefloe/analytics/src/branch/main/repo...
- pat-s 1mo ago
  (founder of codefloe) Numbers are just one thing, what counts is the effective request traffic. We are just as large as we are and can't do anything about it ;) The only thing we can influence is to stay fast from day to day, watch our disk and storage and adjust things if needed. I am quite confident that we can take multiple tens of thousands, if not hundred of thousands of users (with the respective request ratio share of active and dead accounts) with our current hardware stack. We'll see how it goes when we eventually get there.
mbreese 1mo ago
That’s an interesting question - it’s one thing to run an instance of forgejo for a limited user base and another to run at mass public scale. How does someplace like a GitHub/Gitlab go it? Are user accounts or repos sharded across different servers? Is there a different underlying scaling system? If one wanted to run Forgejo “at scale” what would it really require, or does this need to be factored into the design from day one?
- crabmusket 1mo ago
  This recent post that made it to the front page talks a lot about approaches GitHub has taken over its history: https://cursor.com/blog/git-at-any-scale https://cursor.com/blog/git-at-any-scale
  - mbreese 1mo ago
    I ended up finding my own answer (after reading the above). https://nesbitt.io/2026/02/26/git-in-postgres.html https://nesbitt.io/2026/02/26/git-in-postgres.html Following another recent theme, the answer for Forgejo seems to be - just use Postgres.
    - jeremyjh 1mo ago
      That approach was mentioned in the Cursor article. If a KV cache like Redis is too slow for that to work with large repositories, I don't see how Postgres could possibly work.

by mtlynch 1mo ago

jorams 1mo ago

> Performance is similar to when I self-host Forgejo on a dedicated VPS where I'm the only user, which is super fast. I don't mean to be negative, but that's probably because it's pretty much the same thing. Codefloe is tiny. Some quick counting shows it has a grand total of 1012 registered users, including bots, and 1416 public repositories of which the top 3 with the most stars (I know this is a mostly meaningless metric, but for scale) have 27, 13, and 8. It's too small to run into scaling issues.

rererereferred 1mo ago
They keep public records updated quarterly (neat!). Until June they had 774 users and 2090 repos: https://codefloe.com/codefloe/analytics/src/branch/main/reports/2026-Q2/quarterly_report.md https://codefloe.com/codefloe/analytics/src/branch/main/repo...
pat-s 1mo ago
(founder of codefloe) Numbers are just one thing, what counts is the effective request traffic. We are just as large as we are and can't do anything about it ;) The only thing we can influence is to stay fast from day to day, watch our disk and storage and adjust things if needed. I am quite confident that we can take multiple tens of thousands, if not hundred of thousands of users (with the respective request ratio share of active and dead accounts) with our current hardware stack. We'll see how it goes when we eventually get there.

mbreese 1mo ago

That’s an interesting question - it’s one thing to run an instance of forgejo for a limited user base and another to run at mass public scale. How does someplace like a GitHub/Gitlab go it? Are user accounts or repos sharded across different servers? Is there a different underlying scaling system? If one wanted to run Forgejo “at scale” what would it really require, or does this need to be factored into the design from day one?

crabmusket 1mo ago
This recent post that made it to the front page talks a lot about approaches GitHub has taken over its history: https://cursor.com/blog/git-at-any-scale https://cursor.com/blog/git-at-any-scale
- mbreese 1mo ago
  I ended up finding my own answer (after reading the above). https://nesbitt.io/2026/02/26/git-in-postgres.html https://nesbitt.io/2026/02/26/git-in-postgres.html Following another recent theme, the answer for Forgejo seems to be - just use Postgres.
  - jeremyjh 1mo ago
    That approach was mentioned in the Cursor article. If a KV cache like Redis is too slow for that to work with large repositories, I don't see how Postgres could possibly work.