3 ms·
My question is what's next? Without sacrificing (much) memory. We know from TruffleRuby that given enough warmups and lots of memory it could be multiple times
by ksec 3y ago
My question is what's next? Without sacrificing (much) memory. We know from TruffleRuby that given enough warmups and lots of memory it could be multiple times faster than CRuby. And compared to Ruby 3.3 YJIT may be 2-3x faster. But it seems the communities as a whole cares a lot about memory usage.
We know in order to make JIT more useful we need to move some of the Gems from C to Ruby. But other than that do we have anything on the table that will significantly speed up Ruby Rails?
- alberth 3y agoTruffle Ruby is 50-100% faster in most tests. But uses 5-10x more memory. Still has way more upside left to gain. https://railsatscale.com/2023-11-07-yjit-is-the-most-memory-efficient-ruby-jit/ https://railsatscale.com/2023-11-07-yjit-is-the-most-memory-...
- uticus 3y agoNot to mention the warm-up time - the graph in the referenced article is measured in seconds, with max > 20! Can attest, just pulled TruffleRuby (both native and JVM), it is over ten seconds to start a hello world script cold. As in, script being run from command line as needed. These are gains that are only going to make sense for the long-running process crowd.
- parentheses 3y agoIt does make sense in the web server context to optimize for memory first over compute. This could explain the dynamic you called out. Furthermore, the propensity for many popular gems to have native portions makes the trade off even more useful. Regarding JIT being faster, types are the next effective tool IMO. The two drivers I see are: - JIT has more stack frames to optimize away, allowing more optimization - you addressed this one - JIT has more information to limit possible outcomes, therefore finding more opportunities
- schneems 3y ago> But it seems the communities as a whole cares a lot about memory usage. Matz very much sees Ruby as still a general purpose language that still supports scripting as a first tier concern. From that vantage bootup and memory are hugely important. Also providers like Heroku (I work there) charge for memory and the primary way to get parallelism with the GIL/GVL is using multiple processes where memory use can multiply rapidly (literally). > speed up Ruby on Rails? You can look at other communities to get a preview of what might come. Ruby now has “object shapes” like node.js which will benefit the community more once people start using it, enabling warnings and fixing hotspots where instance variables are not declared optimally. Personally, I would like to see rails embrace the power of database backed constraints and fallback to using validation queries only when the database throws an error on commit. You can already saturate a CPU with processes and threads, the biggest bottleneck (IMHO) for most rails apps is still the database. Counterintuitively, pushing those constraints to the database can mean a net decrease in DB computing needed and more overall throughput. Aside from that I think JIT will help do more with fewer resources. Which makes sense when the main YJIT sponsor has a huge server bill and being able to slash it in half more than justifies such long term gambles.
- dalyons 3y agoI’m curious why you think constraints are such a problem? I’ve worked on quite a few large rails apps, and whilst you’re not wrong, the extra traffic from checking constraints has always been a tiny negligible part of overall db traffic.
- schneems 3y agoIt takes two seconds to add a “validated uniqueness” and now for every save or update instead of one SQL command to commit the data you’ve got 2 (multiplied by the number of validations). Plus this validation is weak in that it cannot protect from actual duplicate data. These check queries are individually fast but put a tremendous load on a running app’s database. If you halve the number of queries the database has to process you’ll see more resources to process the slow queries in addition to each commit being faster. It ultimately depends on the read/write patterns of the app, but most non-trivial rails apps do a bunch of writing AND reading. My suggestion is less a “this will change the world forever” and more a “fairly clear win, we just have to do it”. In a prior life I talked Sgrif into implementing it before David caused them to drop Active Record maintenance work. I know the broad strokes but don’t have the need or mandate to implement it, plus the active record internals are pretty gnarly. Tons of modules, very little encapsulation. Very hard to know the correct place to put stuff, so stuff goes wherever. It’s gotten better from some of the work of Yehudah, Aaron, and Sage but AFAIK there’s no one on core who wants to own it right now. Eileen has done a lot of work recently, but I don’t think it’s her primary focus.
- byroot 3y agoThere is still lots of optimizations to make. On the JIT side, there is still no inlining, which opens the door to much more aggressive optimizations. But also on memory as well. There was a lot of improvements done on the Ruby garbage collector for 3.3, but there's still a lot of room for improvement, and a few fine folks at Shopify are looking into making the GC swappable so we'd be able to use mttk GCs with MRI. As for the community caring about memory usage, I wonder how much of that has to do with the default Heroku dynos. Because it's an issue for small scale deployment. Once you scale more, you recoup a lot with CoW etc, so it's much less of a worry.
- claudiug 3y agocan you share on this? :)
- ksec 3y ago>On the JIT side, there is still no inlining, Oh wow. Had no idea there was no inlining. That is potentially another 2-3x performance.
- byroot 3y agoTo be slightly more correct, there is inlining but only of trivial methods that simply return an immediate value or a constant, e.g. class NilClass def blank? true end def present? false end end
- uticus 3y agoDon't forget TruffleRuby's other tricks: parallel code [0] and polyglot language interplay [1] [2]. [0] https://www.graalvm.org/latest/reference-manual/ruby/#aim https://www.graalvm.org/latest/reference-manual/ruby/#aim [1] https://www.graalvm.org/latest/reference-manual/ruby/Polyglot/ https://www.graalvm.org/latest/reference-manual/ruby/Polyglo... [2] https://medium.com/graalvm/graalvm-ten-things-12d9111f307d https://medium.com/graalvm/graalvm-ten-things-12d9111f307d
- mlinksva 3y ago> We know in order to make JIT more useful we need to move some of the Gems from C to Ruby. Just curious, how well do we know this, e.g., theory, experiments, it's being done, or ? It'd be fun if RiiR[uby] were a small part of the overall memory saftey glacier (e.g., https://www.cisa.gov/case-memory-safe-roadmaps https://www.cisa.gov/case-memory-safe-roadmaps)
- TobiasBales 3y agohttps://railsatscale.com/2023-08-29-ruby-outperforms-c/ https://railsatscale.com/2023-08-29-ruby-outperforms-c/ by Aaron comes to mind
- gvkhna 3y agoI added jemalloc to my rails server and it took avg process mem usage of 1-1.5gb down to 400mb.