From 29664f582c93aa9efaa91e347646159ebe359f05 Mon Sep 17 00:00:00 2001 From: Pratik Naik Date: Sat, 10 Jan 2009 04:43:14 +0000 Subject: Fix typos --- railties/doc/guides/html/performance_testing.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'railties/doc/guides/html') diff --git a/railties/doc/guides/html/performance_testing.html b/railties/doc/guides/html/performance_testing.html index 52c2a3599d..54baba3a96 100644 --- a/railties/doc/guides/html/performance_testing.html +++ b/railties/doc/guides/html/performance_testing.html @@ -284,7 +284,7 @@ Learn about various tools facilitating benchmarking and profiling

-

Performance testing is an integral part of the development cycle. It is very important that you don’t make your end users wait for too long before the page is completely loaded. Ensuring a plesant browsing experience to the end users and cutting cost of unnecessary hardwares is important for any web application.

+

Performance testing is an integral part of the development cycle. It is very important that you don’t make your end users wait for too long before the page is completely loaded. Ensuring a pleasant browsing experience to the end users and cutting cost of unnecessary hardwares is important for any web application.

1. Performance Test Cases

@@ -418,7 +418,7 @@ http://www.gnu.org/software/src-highlite --> end end

1.3. Modes

-

Performance tests can be run in two modes : Benchmarking and Profling.

+

Performance tests can be run in two modes : Benchmarking and Profiling.

1.3.1. Benchmarking

Benchmarking helps find out how fast is a performance test. Each test case is run 4 times in benchmarking mode.

To run performance tests in benchmarking mode:

@@ -429,7 +429,7 @@ http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> 
$ rake test:benchmark

1.3.2. Profiling

-

Profiling helps you introspect into a performance test and provide an in-depth picture of the slow and memory hungy parts. Each Test case is run 1 time in profiling mode.

+

Profiling helps you introspect into a performance test and provide an in-depth picture of the slow and memory hungry parts. Each Test case is run 1 time in profiling mode.

To run performance tests in profiling mode:

memory: 832.13 KB objects: 7882
Flat
-

Flat output shows the total amount of time spent in each method. Check ruby prof documentation for a better explaination.

+

Flat output shows the total amount of time spent in each method. Check ruby prof documentation for a better explanation.

Graph
-

Graph output shows how long each method takes to run, which methods call it and which methods it calls. Check ruby prof documentation for a better explaination.

+

Graph output shows how long each method takes to run, which methods call it and which methods it calls. Check ruby prof documentation for a better explanation.

Tree

Tree output is profiling information in calltree format for use by kcachegrind and similar tools.

1.6. Tuning Test Runs

-

By default, each performance test is run 4 times in benchmarking model and 1 time in profiling. However, test runs can easily be configured.

+

By default, each performance test is run 4 times in benchmarking mode and 1 time in profiling. However, test runs can easily be configured.

@@ -552,7 +552,7 @@ http://www.gnu.org/software/src-highlite -->

1.7. Installing GC Patched Ruby

To get the best from Rails performance tests, you need to build a special Ruby binary with some super powers - GC patch for measuring GC Runs/Time and memory/object allocation.

The process is fairly straight forward. If you’ve never compiled a Ruby binary before, follow the following steps to build a ruby binary inside your home directory:

-

1.7.1. Instllation

+

1.7.1. Installation

Compile Ruby and apply this GC Patch:

1.7.2. Download and Extract

@@ -592,7 +592,7 @@ alias gcrails='~/rubygc/bin/rails'

1.7.6. Install rubygems and dependency gems

Download Rubygems and install it from source. Rubygem’s README file should have necessary installation instructions.

-

Additionally, installa the following gems :

+

Additionally, install the following gems :

  • @@ -648,7 +648,7 @@ http://www.gnu.org/software/src-highlite --> by Lorenzo Bettini http://www.lorenzobettini.it http://www.gnu.org/software/src-highlite --> -

    Creating projectem (185.3ms)
+
Creating project (185.3ms)

Please refer to API docs for optional options to benchmark()

2.2. Controller

Similarly, you could use this helper method inside controllers

@@ -684,7 +684,7 @@ http://www.gnu.org/software/src-highlite -->

3. Request Logging

-

Rails log files containt very useful information about the time taken to serve each request. Here’s a typical log file entry:

+

Rails log files contain very useful information about the time taken to serve each request. Here’s a typical log file entry: