Here's the post I teased last week.
TL;DR; Average latency: -5%, p99 latency -10%
Creator https://zestui.com - UI Kit for Ruby on Rails using Tailwind & Phlex
Ruby on Rails Consultant
| Site | https://manu-j.com |
Here's the post I teased last week.
TL;DR; Average latency: -5%, p99 latency -10%
I've just released json 2.7.3 with some bug fixes and lots of performance improvements: https://github.com/ruby/json/releases/tag/v2.7.3
This is my first release after being made maintainer two weeks ago.
If you got some realistic benchmarks in which JSON.dump is significantly slower than an alternative gem, please let me know.
As long as it's not the result of the alternative doing something incorrect, I'll consider it as a bug.
Yes, I love SQLite on Rails as an application architecture. And yes, I truly believe that you should try it for your next project.
But, it isn't a silver bullet and it isn't the right fit for everyone. Plus, even if it is a good fit, there are considerations to be aware of.
@kaspth 3. End to end means, both setup and usage together, like a quick start.
```
# seeds/accounts
donuts = accounts.create :kaspers_donuts, name: "Kasper's Donuts"
```
```
# testcase showing
accounts.kaspers_donuts
```
It's easy to miss the importance of that symbol ` :kaspers_donuts`
@kaspth 3. `users.create :kasper ...` There should be a simple end to end example with just one record. At first glance, I missed the fact this is not plain AR create. The symbol is important as that is used for referencing.
4. Since there can be multiple seeds files with flexibility to create any record, how are symbol clashes handled?