{"id":7773,"date":"2016-03-30T11:45:23","date_gmt":"2016-03-30T11:45:23","guid":{"rendered":"https:\/\/dev.railscarma.com\/get-more-out-of-queries-in-rails-using-bullet-in-just-3-steps\/"},"modified":"2021-06-06T12:30:08","modified_gmt":"2021-06-06T12:30:08","slug":"get-more-out-of-queries-in-rails-using-bullet-in-just-3-steps","status":"publish","type":"post","link":"https:\/\/www.railscarma.com\/sv\/blogg\/tekniska-artiklar\/get-more-out-of-queries-in-rails-using-bullet-in-just-3-steps\/","title":{"rendered":"Get More Out of Queries in Rails Using Bullet in Just 3 Steps"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tHave you ever opened a closet only to have all the inside contents fall all over you? In the programming setting, this is called as \u201cspaghetti code\u201d. These are the kind of codes that are so jumbled that as soon as you make a little change, everything starts falling apart. As much as it is important to write good codes, it is equally important to keep them clean. But when you are developing a large scale application, it becomes difficult to keep your codes clean and organized. In this article you will read to get more out of queries in rails using bullet in just 3 steps\n\nFor a large scale projects with added complexity, manual code refactoring becomes a huge risk and time consuming. Therefore, it is recommended to use third party tools like Bullet Gem for the maintenance, security and optimization of codes.\n\nBullet plugin, developed by Richard Huang for Ruby on Rails, was first used in 2009. And since then, it has proved to be a powerful gem that helps monitor Ruby on Rails applications for performance improvements. Bullet Gem helps in reducing the number of queries that an application makes. It also helps in finding N+1<\/strong> queries in the application during development mode by showing the notifications in browser.\n\n\"image_bullet_gem\"\n\nN+1<\/strong> query problem is a situation when the developer makes extra calls to database when s\/he wants to get a specific associated data over and over again.\n\nFor example,\n
2.2.1 :005 > Message.all.each {|message| message.conversation.sender_id}<\/blockquote>\nThis example gets all messages, then iterates each of those records and tries to get messages conversation from database. Solution for this problem is Bullet plugin, which helps to monitor the queries of the application. It notifies any N+1 scenarios and the unused eager loads. Other common solution for this is to use eager loading methods are preload, includes, eager_load.\n\nExamples for the following methods:-\n
2.2.1 :007 > Message.includes(:conversation).references(:conversations).each { |message| message.conversation.sender_id }\n\n2.2.1 :008 > Message.eager_load(:conversation).each { |message| message.conversation.sender_id }\n\n2.2.1 :009 > Message.preload(:conversation).all.each { |message| message.conversation.sender_id }\n\nEager loading is the solution to the N+1 query problem which makes sure we don\u2019t end up running unnecessary queries while looping through an object.<\/blockquote>\n

Usage &\u00a0Configuration\u00a0Of Bullet Gem :\u00a0<\/strong><\/h4>\nBelow example shows two models; Message and Conversation, wherein a Message consists of many Conversations. Bit of code should be:-\n
In app\/controllers\/messages_controller.rb\n\nclass MessagesController < ApplicationController\ndef index\n@messages = Message.all\nend\nend\nIn app\/views\/messages\/index.html.erb\n\n<h1>Messages<\/h1>\n\n<% @messages.each do |message| %>\n\n<%message.conversations.each do |conversation|%>\n\n<ul class="”message_link”">\n\n<li><%=link_to conversation.sender_id, conversation_path(conversation)%><\/li>\n\n<\/ul>\n\n<%end%>\n\n<% end %><\/blockquote>\nBasically Bullet gem helps to resolving n+1 problem in rails application.<\/strong>\n

Get More Out of Queries in Rails Using Bullet in Just 3 Steps<\/h4>\nStep 1:-\n\nAdd Bullet gem to gemfile and run bundle install,\n
# For code optimisation\n\ngem ‘bullet’, group: [:development, :test]<\/blockquote>\nThe gem should only be used in the development environment, as you wouldn\u2019t want the users of the application getting alerts about the N+1 query problems.\n\nStep 2:-\n\nBullet should be enabled in the application. Just adding the bullet gem won\u2019t notify the bad queries. Configuration is done in the config\/environments\/development.rb.\n
config.after_initialize do\n\nBullet.enable = true\nBullet.alert = true\nBullet.bullet_logger = true\nBullet.console = true\nBullet.rails_logger = true\nBullet.unused_eager_loading_enable = false\nend\nBullet.enable: enable Bullet gem, otherwise do nothing\n\nBullet.alert: pop up a JavaScript alert in the browser\n\nBullet.bullet_logger: log to the Bullet log file (Rails.root\/log\/bullet.log)\n\nBullet.rails_logger: add warnings directly to the Rails log<\/blockquote>\nStep 3:\n\nRestart the server. After step 2, we would see a JavaScript alert popup in the browser with the detected N+1 query. The alert would contain the file that holds the issue and the suggestions to what could be done to override the problem.\nIn Controller,\n
class MessagesController < ApplicationController\n\ndef index\n\n@messages = Message.includes(:conversations)\n\nend\n\nend<\/blockquote>\nRefrences:-<\/strong>\n\nGITHUB LINK: – https:\/\/github.com\/flyerhzm\/bullet<\/a>\n\nOur developers are well versed in doing all kinds of ruby on rails utvecklingsarbete<\/a> och hantera alla typer av projekt. Kontakta oss<\/a> att veta mer om v\u00e5r utvecklingskompetens och de projekt som vi kan hantera.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Prenumerera f\u00f6r de senaste uppdateringarna<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\t\t\t\t\t