graphql-batch
bullet
Our great sponsors
graphql-batch | bullet | |
---|---|---|
3 | 27 | |
1,404 | 6,984 | |
0.4% | - | |
6.2 | 7.7 | |
21 days ago | 3 months ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
graphql-batch
-
The GraphQL N+1 Problem and SQL Window Functions
After recognizing the problem, we brainstormed options to offload some of the work onto the database server to ultimately reduce the Rails application’s memory consumption. One particularly promising avenue involved SQL window functions. After deciding to pursue SQL window functions, we started our work by considering the WindowKeyLoader example described in the graphql-batch repository.
-
N+1 problem will never be an issue with N1Loader gem
Interesting, I've just been researching Dataloader implementations for Ruby and have between trying to decide between GraphQL::Dataloader, graphql-batch and BatchLoader. I'll give this a look as well. Can you also make API calls inside the loaders?
-
"I'm the CTO of a Growing Rails Startup" Ask Me Anything
This is mainly addressed in the last thing but we cache pretty heavily on our REST APIs and for GraphQL we use the graphql-batch gem pretty heavily. Those two things can go a long way. Make sure you're using an APM like Scout to keep an eye on things and then debug the outliers.
bullet
- What was the name of the gem that finds all unindexed foreign keys?
-
Ban 1+N in Django
Rails has Bullet[0] to help identify and warn you against N+1
Does Django have anything active? Quick search revealed nplusone[1] but its been dead since 2018.
[0] https://github.com/flyerhzm/bullet
[1] https://github.com/jmcarp/nplusone
-
Inherited rails app - what the hell are all these rack timeout lines in the log?
Without seeing more of the app, it's tough to say for certain, but one gem you might find helpful is the [bullet](https://github.com/flyerhzm/bullet) gem -- set this up in the app then start browsing around the app in development. If you have any N+1 queries or other minor optimizations that could be done it will inform you about them.
-
A Guide to Memoization in Ruby
Getting rid of N+1 queries - This can help improve the speed of an app. The Bullet or Prosopite gems can give a lending hand here. The N+1 Dilemma — Bullet or Prosopite? entails a brief comparison of both.
-
Understanding N and 1 queries problem
There's a Ruby gem called Bullet that identifies and warns developers about N+1 problems. You can also have it fail tests if detected.
I don't know if the approach is possible with every ORM or if it's just leveraging some Ruby perks, but I can't think of a good reason why you wouldn't use the equivalent everywhere.
https://github.com/flyerhzm/bullet
-
Help with N+1 problem.
You might consider adding the bullet gem as a development requirement and see what it tells you, it's generally pretty good at spotting n-queries and letting you know how to fix them.
-
Understanding and Fixing N+1 Query
As a Rails developer, recently I found Bullet [0] which helps massively in dealing with eager loading. For some reason I expected the framework to manage this sort of thing for me, even when Rails actually does a ton out of the box already. Only while refactoring I picked up on queries dragging performance. Oh well...
[0] https://github.com/flyerhzm/bullet
-
How do you find the cause of slowness in your app?
This is good advice, it'll likely pick out some glaring issues right away. I would generally recommend looking at DB queries here too and recommend Bullet, but most software like DataDog, AppSignal etc will often also point N+1 and issues like it out.
-
Yet Another Post About N + 1 Queries
In order to find all those N + 1 queries that are slowing down in your application, the community recommends using the Bullet gem.
- What are the main suspects in a really slow Rails app?
What are some alternatives?
graphql-guard - Simple authorization gem for GraphQL :lock:
prosopite - :mag: Rails N+1 queries auto-detection with zero false positives / false negatives
graphql-client - A Ruby library for declaring, composing and executing GraphQL queries
rack-mini-profiler - Profiler for your development and production Ruby rack apps.
GQLi - Ruby GraphQL Client for Humans
Peek - Take a peek into your Rails applications.
moql - Mock GraphQL server for fast reliable integration tests.
Derailed Benchmarks - Go faster, off the Rails - Benchmarks for your whole Rails app
BatchLoader - :zap: Powerful tool for avoiding N+1 DB or HTTP queries
benchmark-ips - Provides iteration per second benchmarking for Ruby
Spree Commerce - A headless open source e-commerce platform for global brands
ruby-prof - A ruby profiler. See https://ruby-prof.github.io for more information.