Closed wyattades closed 1 week ago
@wyattades Ping me on Slack. I'd like you to test out https://www.shakacode.com/react-on-rails-pro/ vs execjs.
Here's an invite
@wyattades what's left? you have this PR as draft.
@Judahmeek @ahangarha any good reason this was NEVER FINISHED?
@AbanoubGhadban @Judahmeek should we close?
@alexeyr-ci1 @alexeyr-ci Please advise on the next step for this:
@justin808
Please advise on the next step for this:
In my opinion:
@alexeyr-ci close this after opening issues for your suggestions.
[!IMPORTANT]
Review skipped
Draft detected.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yaml
file in this repository. To trigger a single review, invoke the@coderabbitai review
command.You can disable this status message by setting the
reviews.review_status
tofalse
in the CodeRabbit configuration file.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
The new issue: https://github.com/shakacode/react_on_rails/issues/1658.
Summary
Add some instructions and a script to perform performance benchmarking on some server-side-rendering routes. The goal is to test the performance of different ExecJS runtimes in a real react_on_rails application.
Things to-do before merging. I'd appreciate some guidance to get them working:
Anecdotal results:
I ran this against a route on my app with very expensive React SSR. This is the total roundtrip duration of the request, so it also includes some database IO. Device: M1 Macbook Pro 2021
Pull Request checklist
Add the CHANGELOG entry at the top of the file.
Other Information
This change is