スタンディングデスクが物置になってたのを整理した
$ heroku pg:info DATAB
ASE
=== DATABASE_URL, PG_HOBBY_BASIC_URL
Plan: Hobby-basic
Status: Available
Connections: 8/20
PG Version: 9.6.1
Created: 2017-04-20 18:31 UTC
Data Size: 46.4 MB
Tables: 26
Rows: 52405/10000000 (In compliance)
A spike in traffic seems to have resulted in a spike in response time. I also see H27s.
https://mastodon.zunda.ninja/media/1l5mIgI92JUvSnCqq7E
The spike in traffic was mostly HEAD request to /users/zundan/updates/533 as well as GET to /users/zundan/updates/533.atom from different IP addresses. I suppose the conversation was picked up somewhere and, well, maybe clients rendered the conversation on the fly on their browser?
The first peak in memory use was when I posted a photograph. Mastodon ran some commands on the dyno to process the image which, I suppose, was then posted to S3.
The second spike in memory use was when ImageMagick was ran against an avatar who appeared in Federated timeline. Interesting.
@h12o@blessedgeeks.org 少なくともフォロー関係はそのまま別ドメインに持って行くとわけのわからないことになりそうですよねw