3 ms·
These comments make me want to log off for a bit. Post: we hit scaling issues caused by our failing disks and running image hosting and databases over NFS HN:
by cyberphobe 4y ago
These comments make me want to log off for a bit.
Post: we hit scaling issues caused by our failing disks and running image hosting and databases over NFS
HN: It’s obviously Ruby on Rails fault
- kris-nova 4y agoHi. I wrote the post. Additionally I am responsible for operating Hachyderm (Ruby on Rails) and GitHub (Ruby on rails) for both my free-time and my day job. I can say with certainty that Ruby specifically was not the bottleneck in our case. I do think that the rails paradigm can often lead to interdependent systems. We see this at GitHub and we also see this in Mastodon. Service A will do reads/writes against the same tables in the database that Service B also does. When service A is moved to an isolation zone, it can still impact Service B's performance. In other words, I think any stateful framework with the flexibility that Ruby on Rails encourages bad behavior that can contribute to a noisy neighbor problem. The point I am trying to drive home is that I agree. I can confidently say that Ruby on Rails is not the culprit in our case. To be honest I just ignore anyone who is quick to point fingers and assign blame either technically or personally. Sorry hacker news got you down. If it helps my family and I are making Sunday morning pancakes with my puppy Björn today and we are all wishing you the best day ever.
- cyberphobe 4y agoaw thanks! I follow you on mastodon and it’s been great watching the updates as hachyderm grows
- rbanffy 4y agoIs there any good architectural breakdown of Mastodon software?
- Kye 4y agoIt's surreal. I thought maybe I misread the post or something.