<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Introduction to Flood</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="Flood manual" /><link rel="up" href="index.html" title="Flood manual" /><link rel="prev" href="pr01.html" title="Foreword" /><link rel="next" href="ch02.html" title="Chapter 2. Getting Flood" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. Introduction to Flood</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pr01.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr /></div><div class="chapter" title="Chapter 1. Introduction to Flood"><div class="titlepage"><div><div><h2 class="title"><a id="id2543281"></a>Chapter 1. Introduction to Flood</h2></div></div></div><p>
Flood is a profile-driven HTTP load tester. It is a software that is
capable of generating large amount of web traffic, so you can measure
performance of your web application. Flood can also postprocess web
server responses, so you also can check your web application for
correct behaviour.
</p><p>
Being profile-driven means, that nearly all actions related to creating
and performing a request, are controlled by a set of rules. Those rules
together create a profile. By using different profiles and the same set
of URLs, you might get quite different results. Moreover, particular
profiles are usefull in conjunction with different types of tests. As
far as web applications are concerned, we can distinguish three types
of tests. These are:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
Performance test. This test measures response time of web server.
Desired result is usually a Requests Per Second for given resource
or average for all pages hit.
</li><li class="listitem">
Regression test. This test doublechecks behaviour of web
application, by simulating several user actions (so called URL
paths). It is supposed to give answer to question: Is my web
application working correctly?
</li><li class="listitem">
Web capacity test. This test performs numerous parallel requests,
simulating really heavy ussage of web application. It is supposed
to answer question: does my web application and web server handle
given load?
</li></ol></div><p>
With a little bit of tweaking flood can be useful, regardless of which
type of test you are going to perform.
</p><p>
Flood aims to be modular and extensible. It is fairly easy to write
flood extension providing new functionality. Hence flood can be easily
extended to suit just about everybody needs. Right now it can be used
in most enviroments without the need for writting external modules.
Current flood feature list follows:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">HTTP/1.0 and HTTP/1.1 support</li><li class="listitem">HTTPS support</li><li class="listitem">GET/POST/HEAD support</li><li class="listitem">reponse postprocessing</li><li class="listitem">basic support for AUTH and Cookies</li><li class="listitem">different report modules (different presentation of
results) </li></ul></div><p>
Flood has a homepage available:
<a class="ulink" href="http://httpd.apache.org/test/flood/" target="_top">
http://httpd.apache.org/test/flood</a>. Be sure to check it often
for news and releases. If you have a burning question, or would like
to report a problem (patches welcome), then please subscribe to flood
developemnt mailing list: test-dev@httpd.apache.org, by sending an
empty e-mail to adress:
<code class="email"><<a class="email" href="mailto:test-dev-subscribe@httpd.apache.org">test-dev-subscribe@httpd.apache.org</a>></code>
and following instructions in response.
</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="pr01.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Foreword </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Getting Flood</td></tr></table></div></body></html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
811866d96d7e52c94055a34b3f792ef0
>
files
>
27
