Nick K. nkokkos

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

Introduction

Collection of solutions for streaming via DASH, Dynamic Adaptive Streaming over HTTP, as of November 2014.

Recommended client: Chrome 38

Tool used for encoding live streams: FFmpeg

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

In Rails 3

NOTE: This post now lives (and kept up to date) on my blog: http://hakunin.com/rails3-load-paths

If you add a dir directly under app/

Do nothing. All files in this dir are eager loaded in production and lazy loaded in development by default.

	# lib/tasks/db.rake
	namespace :db do

	desc "Dumps the database to db/APP_NAME.dump"
	task :dump => :environment do
	cmd = nil
	with_config do \|app, host, db, user\|
	cmd = "pg_dump --host #{host} --username #{user} --verbose --clean --no-owner --no-acl --format=c #{db} > #{Rails.root}/db/#{app}.dump"
	end
	puts cmd

	# this monit config goes in /etc/monit/conf.d

	check process puma_master
	with pidfile /data/myapp/current/tmp/puma.pid
	start program = "/etc/monit/scripts/puma start"
	stop program = "/etc/monit/scripts/puma stop"
	group myapp

	check process puma_worker_0
	with pidfile /data/myapp/current/tmp/puma_worker_0.pid

	#/opt/nginx/conf/nginx.conf

	user nginx;
	worker_processes 4;

	#error_log logs/error.log;
	#error_log logs/error.log notice;
	#error_log logs/error.log info;

	pid logs/nginx.pid;

	# Symlink the shared protected folder
	run "ln -nfs #{shared_path}/protected #{latest_release}/protected"

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

	# Gemfile

	gem 'kramdown'