mtl_rubykaigi

Experiences of Rails site stabilized operation Hirotomo Oi Chief Architect Media Technology Lab., Recruit Co.,Ltd.

Agenda • Our “Rails” websites • Software • httpd • Server virtualization • Tips

About Me • Hirotomo Ōi • Chief Architect of infrastructure of web. • And “engekilife.com” tech guy. • And...planning/developing new website.

About MTL • MTL(Media Technology Lab.) is an applied study institute to promote future media communication, and to seek for a sympathetic world for all of us. • One of our focus: Develop prototype web sites, and verify responses and feedbacks through beta releases.

MTL Websites

Software • Httpd for Ruby Apps. • Virtualization

Rails Version • Use various versions. • 1.2.x, 2.0.x, 2.1.x, 2.2.x, 2.3,x... • We choose the newest version at launch time of each site.

httpd • ...Donʼt ﬁx, now trying... • Mongrel • Thin • Passenger • Some sites were changed from Mongrel.

Benchmark Time per request(ms): 31.00 23.25 15.50 7.75 0 Mongrel Passenger

Ruby Version • 1.8.6 • If apps didnʼt work, use another vers. • Ruby Enterprise Edition • for Passenger

Virtualization

Virtualization +

Virtualize servers • Two or more servers can be running on one Web, hardware. App DB cache (memory- (CPU- (IO-bound) bound) • Generally, different bound) resources are put together is good efﬁciency.

virtualize webservers • We are virtualizing web+app tier. • Generally web site A (ruby) site B (php) site C (perl) apps are CPU- bound. • RoR apps need memory.

How many VMs? • Hardware • 16GB memory • 2x Quad Core Xeon • VM Spec • 1GB memory • 10GB disk space • 8 CPU cores available

How many VMs? • Hardware • 16GB memory • 2x Quad Core Xeon • VM Spec 13 • 1GB memory VMs / Hard • 10GB disk space • 8 CPU cores available

How many instances?

How many instances? • 10 Mongrel instances / 1GB mem VM. • 24 Mongrel instances / 2GB mem VM

Tips • DB Tuning • Log rotation • Restart Mongrel

DB Tuning • Developers often forget DB tuning when launch the site. • Developers use ActiveRecord, not connect DB directly.

DB Tuning • Developers often forget DB tuning when launch the site. • Developers use ActiveRecord, not connect DB directly. DO NOT FORGET DATABASE!!

Get Slow Query Log • Step 1: know slow query. • my.cnf [mysqld] log-slow-queries long_query_time=1

EXPLAIN • Step 2: Analysis of slow query • Use “EXPLAIN” mysql> EXPLAIN SELECT...Your Slow Query;

Fix Slow Query • Add Index • Examine to change (ex:divide) the query • Donʼt use join... • Donʼt use subquery...

ex) mysql> show create table rubykaigi_demo G | rubykaigi_demo | CREATE TABLE `rubykaigi_demo` ( `id` int(11) NOT NULL auto_increment, `type` varchar(255) default NULL, `bukken_id` int(11) default NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 |

1) Know Slow Query mysql> SELECT * FROM `rubykaigi_demo` WHERE `type` = 'PlayguideTicketInfoShow' and `bukken_id` = 435; +-------+-------------------------+-----------+ | id | type | bukken_id | +-------+-------------------------+-----------+ | 13139 | PlayguideTicketInfoShow | 435 | +-------+-------------------------+-----------+ 1 row in set (0.01 sec)

2) EXPLAIN mysql> EXPLAIN SELECT * FROM `rubykaigi_demo` WHERE `type` = 'PlayguideTicketInfoShow' and `bukken_id` = 435G id: 1 select_type: SIMPLE table: rubykaigi_demo type: ALL possible_keys: NULL key: NULL key_len: NULL ref: NULL rows: 2299 Extra: Using where

2) EXPLAIN mysql> EXPLAIN SELECT * FROM `rubykaigi_demo` WHERE `type` = 'PlayguideTicketInfoShow' and `bukken_id` = 435G id: 1 select_type: SIMPLE table: rubykaigi_demo type: ALL possible_keys: NULL key: NULL key_len: NULL ref: NULL Not Using Index rows: 2299 Extra: Using where

3) ADD INDEX mysql> ALTER TABLE `rubykaigi_demo` ADD INDEX( `type`, `bukken_id`); Query OK, 1977 rows affected (0.18 sec) Records: 1977 Duplicates: 0 Warnings: 0 or migration: add_index "type_bukken", ["type", "bukken_id"], :name => "type_bukken"

4) RESULT mysql> EXPLAIN SELECT * FROM `rubykaigi_demo` WHERE `type` = 'PlayguideTicketInfoShow' and `bukken_id` = 435G id: 1 select_type: SIMPLE table: rubykaigi_demo type: ref possible_keys: type key: type key_len: 773 ref: const,const rows: 1 Extra: Using where; Using index

4) RESULT mysql> EXPLAIN SELECT * FROM `rubykaigi_demo` WHERE `type` = 'PlayguideTicketInfoShow' and `bukken_id` = 435G id: 1 select_type: SIMPLE table: rubykaigi_demo type: ref possible_keys: type key: type key_len: 773 ref: const,const Using Index rows: 1 Extra: Using where; Using index

Log rotation • “production.log” increase continuously. • Itʼs necessary to rotate logs. ex) logrotate.d conf ﬁle (Your Rails App Log Dir)/*.log { daily missingok rotate 30 compress notifempty copytruncate create 0644 user group }

Log rotation • “production.log” increase continuously. • Itʼs necessary to rotate logs. ex) logrotate.d conf ﬁle (Your Rails App Log Dir)/*.log { daily missingok rotate 30 compress notifempty copytruncate Important! create 0644 user group }

Restart Mongrel • Restart periodically for ﬁx memory leak of Mongrel processes. • Using swap, not only the VM but all VMs on same HW are slow down...

Restart Mongrel • Cron • Logrotate.d • Monit

Agenda • Our “Rails” websites • Softwares • httpd, virtualization,... • Tips • Donʼt forget DB Tuning • Donʼt forget log rotation • Restart Mongrel

...one more thing

Comming Soon!! http://mashupaward.jp/

Thank you Please contact : http://mtl.recruit.co.jp/

http://mtl.recruit.co.jp	188
http://www.soratomo.com	2
http://www.slideshare.net	1
http://mtl.linkerlab.info	1

mtl_rubykaigi

by Hiro Oi on Jul 20, 2009

Accessibility

Tags

Upload Details

Usage Rights

4 Embeds 192

Statistics

mtl_rubykaigi — Presentation Transcript