Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mirakui: High Performance Rails #30

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions mirakui-high_performance_rails/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# High Performance Rails

Why do websites tend to slow down day by day?
Why do people say "Ruby on Rails is slow"?
This presentation is the story that we Cookpad are fighting against the problems.

We rewrote whole codes of Cookpad.com by Ruby on Rails in 2008.
Since then we've been had an aim that we keep the average response time be under 200 ms.

In this presentation, I'll introduce ways to make websites fast using Rails based on our experiences.
And I'll talk about how engineers who are responsible for site's performance should work in their company.

なぜウェブサイトは日に日に遅くなってしまうのでしょうか。
なぜ Ruby on Rails は遅いと言われてしまうのでしょうか。
本プレゼンテーションではこれらの問題に立ち向かいます。

クックパッドでは2008年から Ruby on Rails を採用しており、
平均 200ms 以下のレスポンスタイムを保つという信念を持ち続けてきました。

本プレゼンテーションでは、
Ruby on Rails を使いこなしてウェブサイトを高速にする、われわれの経験に基づいた実践的な手法を紹介します。
また、Webサイトのパフォーマンス担当者は企業においてどう働くべきかについて述べます。

- Preferred presentation day: no preference
- Presentation language: Japanese

## Issei Naruta (@mirakui)

## Cookpad Inc.

An Infrastructure engineer at Cookpad.com in Tokyo, Japan

- [My website](http://d.hatena.ne.jp/mirakui)
- [My twitter](https://twitter.com/#!/mirakui)
- [Past talk slides](http://www.slideshare.net/mirakui)