wvengen

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

briankung

First, add pry-rails to your Gemfile:
https://github.com/rweng/pry-rails

gem 'pry-rails', group: :development

Then you'll want to rebuild your Docker container to install the gems

NullVoxPopuli

Source Code: https://github.com/NullVoxPopuli/rails-NPlusOneTests

Deserialization

deserialization_benchmark.rb

Each of these scenarios just changes the payload to be parsed, and does not change any deserialization options.

No Relationships

royshouvik

import 'dotenv/config';
import { NestFactory } from '@nestjs/core';
import * as repl from 'repl';
import * as Logger from 'purdy';

const LOGGER_OPTIONS = {
  indent: 2,
  depth: 1,
};