hooopo

Firstly, you'll need to install rvm as the buildkite-agent user:

sudo su buildkite-agent
curl -sSL https://get.rvm.io | bash -s stable
source /var/lib/buildkite-agent/.rvm/scripts/rvm
rvm install 2.4.0 && rvm use 2.4.0 && gem install bundler

Secondly, make rvm available to your build commands by adding the following pre-command Buildkite Agent hook:

hooopo

# NewRelic instrumenter for GraphQL-ruby
#
# In your controller:
#  ::NewRelic::Agent.add_custom_attributes({
#    user_id: @user.try(:id),
#    query_string: @query_string,
#    query_arguments: @query_variables
#  })
#
#   @document = self.class.trace_execution_scoped(["GraphQL#parse"]) do

hooopo

FROM alpine:3.4

# skip installing gem documentation
RUN mkdir -p /usr/local/etc \
  && { \
    echo 'install: --no-document'; \
    echo 'update: --no-document'; \
  } >> /usr/local/etc/gemrc

ENV RUBY_MAJOR 2.5

hooopo

-- show running queries (pre 9.2)
SELECT procpid, age(query_start, clock_timestamp()), usename, current_query 
FROM pg_stat_activity 
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' 
ORDER BY query_start desc;

-- show running queries (9.2)
SELECT pid, age(query_start, clock_timestamp()), usename, query 
FROM pg_stat_activity 
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' 

hooopo

# speed up pluck

class ActiveRecord::Relation

  class RailsDateTimeDecoder < PG::SimpleDecoder
    def decode(string, tuple=nil, field=nil)
      if Rails.version >= "4.2.0"
        @caster ||= ActiveRecord::Type::DateTime.new
        @caster.type_cast_from_database(string)
      else

hooopo

#!/usr/bin/env ruby


require 'open-uri'
patchset = ARGV[0]
version  = ARGV[1]

raise 'Please specify a patchset' if patchset.nil?
raise 'Please specify a ruby version' if version.nil?

hooopo

#!/bin/sh

curl -X DELETE 'localhost:9200/i/'

curl -X POST 'localhost:9200/i/' -d '{
  "settings" : {
    "analysis" : {
      "analyzer" : {
        "crazy" : {
          "type" : "custom",

hooopo

My largest Sidekiq application had a memory leak and I was able to find and fix it in just few hours spent on analyzing Ruby's heap. In this post I'll show my profiling setup.

As you might know Ruby 2.1 introduced a few great changes to ObjectSpace, so now it's much easier to find a line of code that is allocating too many objects. Here is great post explaining how it's working.

I was too lazy to set up some seeding and run it locally, so I checked that test suite passes when profiling is enabled and pushed debugging to production. Production environment also suited me better since my jobs data can't be fully random generated.

So, in order to profile your worker, add this to your Sidekiq configuration:

if ENV["PROFILE"]

hooopo

# ElasticSearch Service

description     "ElasticSearch"

start on (net-device-up
          and local-filesystems
          and runlevel [2345])

stop on runlevel [016]

hooopo

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048