Do you thank everyone who makes your software project a success?
Take the time today and explicitly send appreciations to those who don't send you code patches, but help with #design, #localization, user support, defining priorities, community management and so much more!
#NonCodeContributions #FreeSoftware
@74ea0591
Registrations are not actually disabled, but we're limiting certain providers like gmail for the time being, because they have been source of too much spam for us to handle. As you might have ssen, we have removed 22% of all issues in our database because they were recent spam.
Maybe you can look at comment on https://codeberg.org/Codeberg/Community/issues/1297 because this is the discussion for sketching out a permanent solution.
@63417441
We are breaking through the spam waves.
In the past days, we have identified and fixed several performance bummers, an internal meeting from our core team yesterday evening defined a roadmap to fix the rest.
To give you an idea: We are hit by extreme spam posts. In the past day, we removed 15% (!) of all Codeberg issues as spam, and we're still not done.
The removal degrades the performance, sometimes resulting in error 500s. Please reload the page in that case. Thank you for your patience.
@022a7c10 Next.forgejo.org does not replace Codeberg. It is currently a testing instance that also runs on our servers.
If Codeberg is too slow for you, you want better performance, or simply want to move some load there, you can use it for the time being.
Codeberg.org will stay available and we will not stop improving its usability and performance.
Just adding: The performance problem is also worsened by the fact that we are hit with spam waves for several weeks now. Bots create thousands of issues on Codeberg continuously, and although we got more efficient with cleanign it up, it heavily stresses the database.
As per our current investigations, the scaling issue mostly originate from bottlenecks in the software architecture, and "just adding more hardware" does not solve them. We are investigating to scale up and improve performance, but the outcome is open.
The history of these problems is long, and you can start reading here about
- database deadlocks: https://codeberg.org/forgejo/forgejo/issues/220
- human bottlenecks: https://blog.codeberg.org/the-hardest-scaling-issue.html
If you want to help …
@5d47ad8a They don't do much harm, and they don't need to be removed or migrated. Certain very inefficient queries are slowed down by the size of the database (which also inactive repos add to). It's a bug that deserves a fix, and it is open whether it will help much if people migrate away.
The attitude is more: If you only work on personal projects or want to try out the software, consider not stressing Codeberg itself :)
@936e606f It wasn't done yet. The wording is very unfortunate, and the motivation for is is around the edges of "We cannot make any guarantees".
You don't need to use this instance for your important projects, but many people are just playing around or publishing their dotfiles somewhere. They can probably live with some caveats.
#Codeberg suffers from high load, and #Forgejo / #Gitea does not scale very well. We identify bottlenecks from time to time, but it's hard to stay ahead.
If your project does not need to be on Codeberg, consider using https://next.forgejo.org instead.
- it runs on the same hardware and stack managed by Codeberg
- it has better performance
- dogfooding this instance helps the Forgejo developers (please report problems as you encounter them)
- it reduces the load on Codeberg
Read on …
As per our current investigations, the scaling issue mostly originate from bottlenecks in the software architecture, and "just adding more hardware" does not solve them. We are investigating to scale up and improve performance, but the outcome is open.
The history of these problems is long, and you can start reading here about
- database deadlocks: https://codeberg.org/forgejo/forgejo/issues/220
- human bottlenecks: https://blog.codeberg.org/the-hardest-scaling-issue.html
If you want to help …
We are entering phase 2: We are shutting down the machine for hardware maintenance.
We apologize for the inconvenience. Next time we boot up, you'll see more RAM and faster storage!
Oddbean new post about login | logout
Notes by Codeberg.org | export