Please Do Not Use Asset Sync | Heroku Dev Center
Additional ResourcesHomeElementsProductsPricingCareersHelpStatusEventsPodcastsCompliance CenterHeroku BlogHeroku Blog Find out what's new with Heroku on our blog. Visit Blog Using Asset Sync can cause failures. Heroku recommends using a CDN instead of asset_sync whenever possible. The asset sync gem uploads your assets (images, CSS, JavaScript) to a third party file store such as S3. From there, y
Caching Strategies for Rails | Heroku Dev Center
Web applications will typically have a small handful of pages that take an exceptionally long time to load. On Heroku, long running requests can tie up your dynos and seriously effect application performance. Use New Relic to determine which pages and database requests are running slowly (see the Web Transactions and Database tabs). Examine the longest running requests. If they are caused by slow
Concurrency and Database Connections in Ruby with ActiveRecord | Heroku Dev Center
When increasing concurrency by using a multi-threaded web server like Puma, or multi-process web server like Unicorn, you must be aware of the number of connections your app holds to the database and how many connections the database can accept. Each thread or process requires a different connection to the database. To accommodate this, Active Record provides a connection pool that can hold severa
Puma is Now the Recommended Ruby Webserver | Heroku Dev Center
Puma is Now the Recommended Ruby WebserverChange effective on 23 January 2015 Heroku now recommends using the Puma webserver. The previously recommended webserver, Unicorn, is susceptible to slow client attacks. If you are using Unicorn on Heroku please migrate to Puma. For more information read Deploying Rails Applications with the Puma Web Server.
PostgreSQL Concurrency with MVCC | Heroku Dev Center
Additional ResourcesHomeElementsProductsPricingCareersHelpStatusEventsPodcastsCompliance CenterHeroku BlogHeroku Blog Find out what's new with Heroku on our blog. Visit Blog One of the big selling points of Postgres is how it handles concurrency. The promise is simple: reads never block writes and vice versa. Postgres achieves this via a mechanism called Multi Version Concurrency Control. This tec
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
