Topic: Leveraging view assets precompile and caching
We are new to scaling Ruby on Rails, but we have a very well performing (simple DB) site and scale our machine to 100% CPU, and have balanced our Apache and Ruby process to about 60 web requests per second, on a simple 4 core single slot Intel System. We are using 2 APM system to fine tune and learn, New Relic and Tracelytics. Each of them points to the render time as the primary culprit of the transaction time, over 100ms, the Apache time and Active Record time is each under 10 ms.
I figured I could get render (or html/template/view) processing well under 100ms as well with assets precompile and assets caching. So we tried.
1. bundle exec rake assets:precompile
2. bundle install
3, Railsenv is set to "production" in the apache virtual configuration
4. The production.rb is the delivered one and it has all the right settings, and I have rails static asset server turned off.
3. restarted the environment
But still New Relic and Tracelytics each show 100-120 ms in "view processing" time.
We are on Ubuntu with Apache 2.2 -> Phusion Passenger 3.0.18 -> Rails 3.2.8
How can I truly tell if I am serving static assets?
Last edited by fxober (2013-01-23 19:03:46)