I am trying to understand the last line from an action log in
development mode. I have the following line and understand the view
and DB as the length of time it takes to process the view and the db
access. But what is the rest of the time?
Completed in 923ms (View: 220, DB: 45) | 200 OK [http://localhost:3000/
properties/2-hale-kamaole]
923 is total time it took since the request arrived untill it was
cmpletely served.
220 is how long it took to process the view
45 is the time the db took
200 is not a time is the HTTP header (200 means its all good to go,
404 means its not … etc)
So sory! i didnt read that last line! Didnt mean to be so obvious.
there are more factors to completing a request than view and db (such
as watiting time). and if you do the same test on a heavily loaded
machine, it would take longer.
I am trying to understand the last line from an action log in
development mode. I have the following line and understand the view
and DB as the length of time it takes to process the view and the db
access. But what is the rest of the time?
Completed in 923ms (View: 220, DB: 45) | 200 OK [http://localhost:3000/
properties/2-hale-kamaole]
I get 265 ms but the total is 923ms. a long time.
Controller code, model code that didn’t hit the database etc… In
development there’s also all the reloading of your source code.
Waiting time? What waiting time? I have run the test many times and
most are in this range. I am trying to figure out why it is taking so
long to complete. The current time is unacceptable.
So sory! i didnt read that last line! Didnt mean to be so obvious.
there are more factors to completing a request than view and db (such
as watiting time). and if you do the same test on a heavily loaded
machine, it would take longer.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.