2010-12-16 72 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