Skip to content

Comment on Twitter Said To Be Abandoning Ruby on Railsparent

Comments

The bottleneck/stress-point is almost certainly the unique IO patterns and latency expectations. I doubt CPU is the issue or that C is necessary; instead they need to figure out the right fanning/batching algorithms, and buy gobs of RAM and use it efficiently.

With their recent fundraising, they might even be able to run a couple parallel fixup projects in competition, and let the best win.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.