mulhoon

$('#container').highcharts({
    chart: {
      alignTicks: true,           // When using multiple axis, the ticks of two or more opposite axes will automatically be aligned by adding ticks to the axis or axes with the least ticks.
      animation: true,            // Set the overall animation for all chart updating. Animation can be disabled throughout the chart by setting it to false here.
      backgroundColor: '#FFF',    // The background color or gradient for the outer chart area.
      borderColor: '#4572A7',     // The color of the outer chart border.
      borderRadius: 5,            // The corner radius of the outer chart border. In export, the radius defaults to 0. Defaults to 5.
      borderWidth: 0,             // The pixel width of the outer chart border.
      className: null,            // A CSS class name to apply to the charts container div, allowing unique CSS styling for each chart.
      defaultSeriesType: 'line',  // Alias of type.

krasnoukhov

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"]

nofxx

# Clickable Files by nofxx
"""files.py - Clickable Files URIs open in Emacs"""
import re
import terminatorlib.plugin as plugin
import subprocess

# Every plugin you want Terminator to load *must* be listed in 'AVAILABLE'
AVAILABLE = ['FileURLHandler']

class FileURLHandler(plugin.URLHandler):