diff options
Diffstat (limited to 'railties/doc/guides/benchmarking_and_profiling/basics.txt')
| -rw-r--r-- | railties/doc/guides/benchmarking_and_profiling/basics.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/railties/doc/guides/benchmarking_and_profiling/basics.txt b/railties/doc/guides/benchmarking_and_profiling/basics.txt index 24174efc7e..ee27a059cd 100644 --- a/railties/doc/guides/benchmarking_and_profiling/basics.txt +++ b/railties/doc/guides/benchmarking_and_profiling/basics.txt @@ -1,7 +1,7 @@ == On The Road to Optimization == === Looking at the log file in regards to optimization === - You actually have been gathering data for benchmarking throughout your development cycle. Your logs are not just for error detection they also contain very useful information on how speedy your action is behaving. + You actually have been gathering data for benchmarking throughout your development cycle. Your log files are not just for error detection they also contain very useful information on how speedy your action is behaving. .Regular Log Output ============================================================================ @@ -34,7 +34,7 @@ Rendering: 0.00819 (19%) is the amount in milliseconds and the percentage of to DB: 0.00757 (17%) is the amount in milliseconds and the percentage of total time needed to complete the action for querying the database -Pretty easy right. But wait 17+19 equals 36. 36%! where is the rest of the time going? The rest of the time is being spent processing the controller. Which is usually what takes up the bulk of the action +Pretty easy right. But wait 17+19 equals 36. 36%! where is the rest of the time going? The rest of the time is being spent processing the controller. It is not shown but it is easy to calculate. Usually there is where most of your time ends on well functions actions. === Why the Log File on it's Own is not Helpful === @@ -46,7 +46,7 @@ But there is something else we must consider. Is Completed in 0.04310 (23 reqs/sec) a good time. Seems like it doesn't it. 43 ms does not outrageous time for a dynamic page load. But is this a dynamic page load. Maybe it was all cached. In which case this is very slow. Or maybe I'm running on five year old equipment and this is actually blazing fast for my G3. The truth is that we can't answer the question given the data. This is part of benchmarking. We need a baseline. Through comparative analysis of all your pages in your app, and an simple dynamic page for a control we can determine how fast your pages are actually running and if any of them need to be optimized. -And now for something completely different a statistic lesson. +And now for something completely different a short statistic lesson. |