6 ms·
> 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 p
by jorams 23d 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 23d agoThey 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 20d 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.