All the R14s on Heroku-16 stack. I should decrease number of threads from 3 to 2.
$ heroku config:set MAX_THREADS=2 https://mastodon.zunda.ninja/media/9rfhoc55PzmmJtniAnI
All the R14s on Heroku-16 stack. I should decrease number of threads from 3 to 2.
$ heroku config:set MAX_THREADS=2 https://mastodon.zunda.ninja/media/9rfhoc55PzmmJtniAnI
Ah, OK, I should retain DB_POOL at, say, 5:
ActiveRecord::ConnectionTimeoutError: could not obtain a connection from the pool within 5.000 seconds
$ git grep DB_POOL
config/database.yml: pool: <%= ENV["DB_POOL"] || ENV['MAX_THREADS'] || 5 %>
$ heroku config:set DB_POOL=5
$ git pull upstream
$ git rebase upstream/master
$ git rev-parse master
ebbbcfef1c805efbf0c6b80e4e9f1d7bcddba2ba
$ git checkout zunda-ninja-on-heroku
$ git merge master
$ git push
$ git checkout master
$ git push
and this instance is on 833ae4f in zunda-ninja-on-heroku branch.
It seems that replying to a CW toot posted the original toot without the reply.
how about replying to a normal toot?
Deployed the branch with a39e719b392f2a2de3415850ff04deeefd3e8742 from upstream/master merged.
Current status:
$ heroku pg:info DATABASE
=== 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: 31.2 MB
Tables: 26
Rows: 30457/10000000 (In compliance)
It seems that the latest deploy (v51 that has a39e71, i.e., v1.3.1+, from upstream/master) shows elevated tail in response time.
