Futamura projections of Rails applications

Not sure where the best place is to have discussions on ruby-bench, but I'm exploring ideas related to the railsbench demo contained in this repository and perhaps there may be something worth collaborating or following up on.

Quick start:

curl -sL https://rubys.github.io/roundhouse/browse/ruby.tgz | tar xz
cd ruby
bundle install
make seed assets
BLOG_DB=tmp/blog.sqlite3 bundle exec puma -C config/puma.rb

This is the quintessential Rails blog demo modernized with Tailwind CSS, Turbo Streams, and Action Cable - open multiple windows and make changes and see pages update live. All running as a pure Ruby application (no Rails) which is automatically generated from the original Rails source.

Benchmark results show high requests/second with slightly lower memory usage. Section 3 of this page may be of particular interest. There may be opportunities for more parallelism or optimizations - suggestions welcome.

The Ruby JRuby Was Built to Run provides more background on the Ruby to Ruby transformation and the points made in the post apply equally to MRI CRuby.

Futamura projections describes the overall technique.

Commencez par la démo de railsbench à l’aide des commandes de configuration indiquées, puis examinez les résultats du benchmark, en particulier la Section 3, ainsi que le contexte lié aux Futamura projections. L’issue ne définit ni changement spécifique, ni critère d’acceptation, ni objectif d’implémentation ; il faudrait convenir de ce que signifie « done » avant de commencer le travail.