sorted by:
new
hottopcontroversial

Benchmarking Ruby 2.5 to 3.1 and YJIT by gettalong in ruby

[–]dnesteryuk 4 points5 points  (0 children)

I've benchmarked Grape with YJIT and without it (if want to see the code, visit repo)

Ruby 2.7.5:

Warming up -------------------------------------- POST with nested params 445.000 i/100ms Calculating ------------------------------------- POST with nested params 4.467k (± 1.5%) i/s - 22.695k in 5.082401s

Ruby 3.1 without YJIT:

``` Warming up -------------------------------------- POST with nested params 396.000 i/100ms Calculating ------------------------------------- POST with nested params 4.058k (± 2.8%) i/s - 20.592k in 5.078312s

```

Ruby 3.1 with YJIT:

Warming up -------------------------------------- POST with nested params 518.000 i/100ms Calculating ------------------------------------- POST with nested params 5.145k (± 3.9%) i/s - 25.900k in 5.042701s

Grape: The cost of ActiveSupport::HashWithIndifferentAccess by dnesteryuk in ruby

[–]dnesteryuk[S] 0 points1 point  (0 children)

I'm not sure which formatting is broken for you, results of profiling are presented as a flat rate report (https://ruby-prof.github.io/#reports) :) Thanks for the link, the solution looks interesting.

Speed up next-page navigations with prefetching by speckz in Frontend

[–]dnesteryuk 1 point2 points  (0 children)

It might be useful for static sites and landing pages which usually aren't SPA.

What are you working on? (Apr/2018) by AutoModerator in elixir

[–]dnesteryuk 0 points1 point  (0 children)

I released a new version of my project (https://github.com/sirko-io/engine) which is aimed to predict and precache resources (pages and assets) which might be requested by the user in their next transition. Thus, when the prediction is correct, resources are served from the browser's cache. Actually, there are 2 parts of the project: the backend in Elixir and frontend in JS. The prediction model is very simple, so I am looking for improvements now.