Note that there are some explanatory texts on larger screens.

plurals
  1. POperformance testing - test:profile vs test:benchmark, wall time vs process time
    primarykey
    data
    text
    <p>I am new to performance testing on rails. Can somebody explain the difference between wall time and process time? More importantly what is the difference between the time results that come from test:benchmark and test:profile. There is clearly a major difference, which I haven't gleaned from the docs. A few facts:</p> <p>When I run rake test:benchmark, I get:</p> <pre><code>EditorTest#test_augment_large_doc (618 ms warmup) wall_time: 554 ms memory: 0.00 KB objects: 0 gc_runs: 0 gc_time: 0.00 ms </code></pre> <p>When I run rake test:profile, I get:</p> <pre><code>EditorTest#test_augment_large_doc (617 ms warmup) process_time: 1.74 sec memory: unsupported objects: unsupported </code></pre> <p>I have read:</p> <ul> <li><a href="http://guides.rubyonrails.org/performance_testing.html#generating-performance-tests" rel="nofollow">http://guides.rubyonrails.org/performance_testing.html#generating-performance-tests</a></li> <li><a href="http://ruby-prof.rubyforge.org/" rel="nofollow">http://ruby-prof.rubyforge.org/</a></li> </ul> <p>... but I still don't understand the fundamental difference between these types of performance tests and why the times differ so much.</p> <p>A couple more things: when I tail my development log, I get a time typically a bit higher (.1 secs) than the wall time from test:benchmark. And, when I look at XHR request times in firebug or chrome, I get a time typically .3 secs higher.</p> <p>Thanks in advance!</p> <p>[edit]</p> <p>hmmm... no responses. Any comments? Is this a tool rails developers frequently use? Is the difference irrelevant for the optimization process?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload