• user warning: Table './avideotutorial/votingapi_vote' is marked as crashed and last (automatic?) repair failed query: SELECT * FROM votingapi_vote v WHERE 1 = 1 AND v.content_type = 'node' AND v.content_id = 202 AND v.tag = 'upndown' AND v.uid = 0 AND v.vote_source = '18.208.203.36' AND v.timestamp >= 1710826555 in /data/avideotutorial/sites/all/modules/votingapi/votingapi.module on line 557.
  • user warning: Table './avideotutorial/votingapi_vote' is marked as crashed and last (automatic?) repair failed query: SELECT * FROM votingapi_vote v WHERE 1 = 1 AND v.content_type = 'node' AND v.content_id = 202 AND v.tag = 'upndown' AND v.uid = 0 AND v.vote_source = '18.208.203.36' AND v.timestamp >= 1710826555 in /data/avideotutorial/sites/all/modules/votingapi/votingapi.module on line 557.

High Performance Ruby on Rails and MySQL


High Performance Ruby on Rails and MySQL
David Berube (Berube Consulting)

From the official conference description is at http://www.mysqlconf.com/mysql2009/public/schedule/detail/6942

MySQL is among the fastest relational databases commonly available today; unfortunately, the database alone is only part of the picture. For todays web applications, the one weak link in the entire performance chain from the network to the web application and ending in the database can cause an entire application to seem slow.

Unfortunately, Ruby on Rails on exacerbates this problem: Rails makes it easy to develop complicated web applications fast, but it also makes it easy to access your databases in an extremely inefficient manner. Thousands of queries may be generated when just a few are necessary. Even if you can get past that problem, ActiveRecord itself can be a problem: it may create thousands or even millions of objects, and in many situations such as bulk loading or updating data this can cause a serious performance problem. Replacing ActiveRecord in key situations can result in the length of batch process going from days to minutes.

This talk will demonstrate the following for your attendees: * What kind of performance problems am I likely to run into with Rails? * How can I tell if Rails is responsible for my performance problems? * What specific techniques can I use to reduce the number of queries and the size of ActiveRecord objects returned? * What are some real world examples of ActiveRecord speedup using these techniques?


See video

Comments

Post new comment

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options