Skip to content

Instantly share code, notes, and snippets.

Check Your I/O Scheduler
If you are using SSDs, make sure your OS I/O scheduler is configured correctly. When you write data to disk, the I/O scheduler decides when that data is actually sent to the disk. The default under most *nix distributions is a scheduler called cfq (Completely Fair Queuing).
This scheduler allocates time slices to each process, and then optimizes the delivery of these various queues to the disk. It is optimized for spinning media: the nature of rotating platters means it is more efficient to write data to disk based on physical layout.
This is inefficient for SSD, however, since there are no spinning platters involved. Instead, deadline or noop should be used instead. The deadline scheduler optimizes based on how long writes have been pending, while noop is just a simple FIFO queue.
This simple change can have dramatic impacts. We’ve seen a 500-fold improvement to write throughput just by using the correct scheduler.
Link: https://www.elastic.co/guide/en/elasticsearch/guide/2.x/har

Keybase proof

I hereby claim:

  • I am devdetonator on github.
  • I am devdetonator (https://keybase.io/devdetonator) on keybase.
  • I have a public key ASCkKElgnpIX5iJo9eyN4IrUuE6_6V7-BJeoKF4zZ_IGpgo

To claim this, I am signing this object:

@devdetonator
devdetonator / clean-osx-install.md
Created July 20, 2016 13:11 — forked from marcuslilja/clean-osx-install.md
Clean Install – OS X 10.11 El Capitan

Mac OS X 10.11 (El Capitan)

Some text to describe it all here.

Applications

A simple list of regular applications and plugins.

Regular downloads

@devdetonator
devdetonator / php.ini
Created April 12, 2016 11:45 — forked from jsifalda/php.ini
Xdebug: nginx (php-fpm) and phpStorm configuration
zend_extension="/usr/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so"
[xdebug]
xdebug.idekey="macgdbp"
xdebug.remote_enable=1
xdebug.remote_host="localhost"
xdebug.remote_port=9089
xdebug.remote_handler="dbgp"
@devdetonator
devdetonator / README.md
Created March 15, 2016 23:50 — forked from ismell/README.md
Ubuntu Upstart Script for Team City

Ubuntu Upstart Script for Team City

  1. Install TeamCity.conf and TeamCityAgent.conf in /etc/init/

  2. Create TeamCity in /etc/default/TeamCity

  3. Make sure TEAMCITY_DATA_PATH and TEAMCITY_SERVER_PATH are owned by www-data

  4. Start TeamCity

     sudo service TeamCity start