yorickdowne

Overview

Syncing an Ethereum node is largely reliant on latency and IOPS, I/O Per Second, of the storage. Budget SSDs will struggle to an extent, and some won't be able to sync at all. IOPS can roughly be used as proxy of / predictor for latency. Measuring latency directly is arguably better.

This document aims to snapshot some known good and known bad models.

The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.

For size, 4TB is a very conservative choice. The smaller 2TB drive should last an Ethereum full node until at least sometime 2026, with the [pre-merge history expiry](https://hackmd.io/@hBXHLw_9Qq2va4pRt

FradSer

The latest beta (3.5) includes separate color settings for light & dark mode. Toggling dark mode automatically switches colors.

Vist iTerm2 homepage or use brew install iterm2-beta to download the beta. Thanks @stefanwascoding.

---

1. Add switch_automatic.py to ~/Library/ApplicationSupport/iTerm2/Scripts/AutoLaunch with:

rfikki

admin.addPeer("enode://372cc9da5d91b0cf19c8773f3197ba98059041a709ca36d643d37942d9457d34eaee58f90d23bf3e20a7b777a2c4b9247e1aa301f493b2de5d53b3ddb5cb7ac7@116.202.210.165:57840");
admin.addPeer("enode://88897be3c4a05b94813f69a8802d988cedaff711c9238811a0a38649b88703668686b4aee13ad066409a95a5368100528adf4fa7a0af7efd2a9ea194711a4da1@193.26.156.253:34896");
admin.addPeer("enode://357d1b6c71fd1a9669a0d20aae53d18b69676a0eb2baa2209806932e7e1f1e20d154a823b1e200cb8434e17dcf837c4772f2231136b0164ccaaeeabf009dc2e0@119.8.107.226:16861");
admin.addPeer("enode://3a98d3f88d7b4bf0d7251e6de7e43ae803a5ec260c35e02b526681af4d8b2e660dc3d10e64235a1551f35fa18de91cd22f5ed2c364a3e683b442f3a352bedd50@47.24.140.226:30303");
admin.addPeer("enode://c9cd1b2514fc616abf0a1504e858235438ae0c3bd8d8af562e522eb5e9df703dbc516cd499232a230c107e611ec052a1860cbd3be2636ac4fb24715392c952cd@87.117.249.243:30303");
admin.addPeer("enode://f303f44626b5989f240145086a35c2a94f46d923a9590d847814c703a44940b4367a9098e8b02cbc204d9798bbf6c3dfa04b8224870170be2a9d9a5d62

snorfalorpagus

"""
This script demonstrates the use of nested transactions in SQLAlchemy, including
a workaround for an issue with the SQLite backend.

References:
http://docs.sqlalchemy.org/en/latest/orm/session_transaction.html#using-savepoint
http://docs.sqlalchemy.org/en/latest/dialects/sqlite.html#serializable-isolation-savepoints-transactional-ddl
"""

from sqlalchemy import Column, String, Integer

lars-tiede

import threading
import asyncio

async def run_coro_threadsafe(self, coro, other_loop, our_loop = None):
    """Schedules coro in other_loop, awaits until coro has run and returns
    its result.
    """
    loop = our_loop or asyncio.get_event_loop()

    # schedule coro safely in other_loop, get a concurrent.future back

coderofsalvation

# updates an environment variable of a running process (needs sudo)
# example: sudo export_pid <variable=value> <pid>

export_process(){
  script=/tmp/.gdb.$2
  echo -e "attach $2\ncall putenv (\"$1\")\ndetach\n" > $script
  gdb -q -batch -x $script &>/dev/null
  rm $script
}

achillean