The talk was on best practices and some tips on looking for problems and how the panelists worked around them. There are no “magic” bullet like Ruby or RoR has 🙂
- Watch out when using ActiveRecord. It make it too easy to use DB. It make it too easy to use DB. One more time, it make it too easy to use DB.
Essentially, ActiveRecord and DB is not always the right tool. Sometime using other tool could work better for a particular problem.
- Using Redis as a queueing system, to buffer writes, which later go to DB. (this is what Blitz, Bleacher Report use to increase their performance).
- Use NoSQL (CouchBase, Mongo and Cassandara were mentioned as being used by panelists).
- Cache results as much as possible. Don’t hit DB all the time.
- Hand optimize queries might be needed. ActiveRecord is not the best at generating optimized DB calls.
- Cache as much as possible. Bleacher Reports put in caching layer everywhere, memcache, front end web cache, etc. They also have scripts that pre-warmed their cache (“goal is to never have users be the one who triggered a cache request”).
Use the cache in newer RoR (3.2).
- Write code in ways that make it easy to update to latest Ruby and RoR.
Ruby EE has flags to allow you to use more memory for internal cache. Sometime it make sense to test for and try different memory configuration there (based on 2 panelists’ experiences).RoR 3.2 has good Rack/Rails cache. Read the doc and use them.
- Background processes.
- Use bg proc whenever possible.
- Anytime you need to make calls to external website (external API), use a bg process, to not tie up your RoR web process.
- Blitz put jobs into Redis queue, then bg server check Q for job, run it and put partial results back into Redis, Ajax call then check and format/display result to web client.
- Bleacher Reports and Mixbooks also do similar things. They use Redis as a job queueing system, among other things (see 1 above).
- They all mention using other web server for production (not using webrick). The following were mentioned as being used by panelists.
- Related to (ActiveRecord) above is the N+1 problem. Where you add 1 line of code and the DB calls increased manifold.
- Advice essentially say to develop and use coding best practices and train developers to look out for them.
- There is a possible test that can be use to automated looking out for N+1 issue.
- Solving n+1 problem with special tests: http://en.oreilly.com/rails2009/public/schedule/detail/8615 Query testing – see PDF of slides page 75
- Panelists all recommended RSpec for automated testing.
- Monitoring for issues and performance.
- All panelists point to NewRelic as the tool they use all the time.
- The host of the meeting Blitz also did a marketing spiel on their tool to use for performance testing (it look really good, and available as a plugin on Heroku). I am going to test it and see about using it for performance/load testing our site.
- For ease of scaling infrastructure, leverage AWS EC2, Heroku, Engine Yard and other cloud providers.