Someone was asking me about comparing the HoC and Render Props patterns (and their shortcomings) to hooks. I might leave this up as a public gist for others if it's helpful.
tldr;
Issues with HoC:
/** | |
* Get lost unsaved buffers in Atom editor | |
* | |
* Load text content of all unsaved buffers stored by Atom for any project in IndexedDB and print it to Developers tools console | |
* | |
* Author: David Ferenczy Rogožan (https://ferenczy.cz) | |
* | |
* Instructions: | |
* | |
* 1. Start Atom |
#!/usr/bin/env bash | |
set -o errexit | |
echo $(date):Random read | |
fio --filename=test --sync=1 --rw=randread --bs=4k --numjobs=1 \ | |
--iodepth=4 --group_reporting --name=test --filesize=10G --runtime=300 && rm test | |
echo $(date):Random write | |
fio --filename=test --sync=1 --rw=randwrite --bs=4k --numjobs=1 \ |
#!/bin/bash | |
curl -L -O https://downloads.redisinsight.redislabs.com/latest/redisinsight-linux64 | |
chmod +x redisinsight-linux64 | |
./redisinsight-linux64 |
{ | |
"info": { | |
"_postman_id": "7eaf462d-6713-446d-9872-0c5ecef206d8", | |
"name": "mPulse", | |
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json" | |
}, | |
"item": [ | |
{ | |
"name": "Annotations", | |
"item": [ |
There is already a guide on scaling your Mastodon server up. This is a short guide on scaling your Mastodon server down.
I.e., maybe you want to run a small instance of <100 active users, and you want to keep your cloud costs reasonable.
So you might be running everything on a single machine, with limited memory and CPU. (In my case, I was using a t3.medium
instance with 2 vCPUs and 4GB of RAM.) How
do you do this?
Note that I'm not a Ruby or Sidekiq expert, and most of this stuff I figured out through trial and error.