2010-12-16 54 views
2

我运行railscasts网站的本地副本,以熟悉的轨道3.我正在研究开发日志,我点击后四周,这里就是我看到:响应时间的其余部分来自哪里?

Started GET "/" for 127.0.0.1 at 2010-12-16 14:17:07 -0500 
    Processing by EpisodesController#index as HTML 
    Episode Load (0.5ms) SELECT "episodes".* FROM "episodes" WHERE (published_at <= '2010-12-16 19:17:07.872204') ORDER BY position DESC LIMIT 10 OFFSET 0 
Rendered shared/_navigation.html.erb (1.4ms) 
    Sponsor Load (0.2ms) SELECT "sponsors".* FROM "sponsors" WHERE (active = 't') 
    Tag Load (0.1ms) SELECT "tags".* FROM "tags" ORDER BY name 
Rendered shared/_side.html.erb (4.2ms) 
Rendered episodes/index.html.erb within layouts/application (9.8ms) 
Completed 200 OK in 117ms (Views: 12.7ms | ActiveRecord: 0.8ms | Sphinx: 0.0ms) 

哪里其余响应时间从何而来?它表示完整请求的时间为117毫秒,看起来它记录了所有数据库查询。剩下的时间真的只是控制器逻辑吗?

回答

3

问题很简单。这是一个开发日志片段,因此所有这些额外的时间都被轨道重新加载类所吞噬。

1

的其余时间将去:

  • 控制器,视图,模型逻辑
  • 发送/接收的HTTP数据
  • Rails内部
  • 日志记录,打印控制台
+0

模型逻辑与ActiveRecord时间的区别是什么? 也不是视图时间占 – Clinton 2011-07-05 05:32:51