What was the SQL bottleneck you found at test 16?
Andrew Dixon
1

Hi Andrew — we were running a rails counter_cache on media items associated with users. This caused a extra reads/writes to the user table every time a new media item was added, and so the user table ended up being a bottleneck for most read/write operations. We implement this use case totally out of band of Postgres using ElasticSearch.