WGET Benchmark

This benchmark uses the Linux wget tool to "spider" the ]po[ server. As a result, a large number of frequently used pages is executed. Please note that this benchmark heavily more then others on the ]po[ application data, so that the results might vary more then other ]po[ benchmarks.

This benchmark is particularly well suitable to test the scalability of a system if you execute more then one wget command in parallel.

Benchmark Setup

To setup the benchmark, you will need to setup a page /web/projop/www/wget.tcl with the following two lines of content:

ad_user_login 8864
ad_returnredirect "/intranet/"

• "8864" is the ID of the "Ben Bigboss" account. You may use a different user ID in order to benchmark different page profiles. For example, you could use 8811 "Angelique Picard" for a more restricted selection of pages of 624 for "System Administrator" in order to include administration pages.
• "/intranet/" refers to the "Home" page of ]po[. Starting with this page will allow to spider the most frequently used pages. However, you could also choose "/intranet/projects/" to concentrate on projects.
  

Once the wget.tcl file is set up, please execute wget with the following parameters:

time wget -r --retry-connrefused --tries=3 --waitretry=3
          --spider --timeout=3 --level=1 --keep-session-cookies
          --exclude-directories register http://your_server/wget

• "--level=1" means that wget will only descent one level from the initial "/intranet" page. This setting is useful for this benchmark, because --level=2 might take hours to complete.
• "--exclude-directories regisger" tells wget to exclude the /register/ pages which includes the "/register/logout" page which we want to avoid.

Benchmark Results

Single Processor, single wget, --level=1

On a single processor quad-core server with ]po[ V3.5.0 "native" and parameters: user_id=8264 and --level=1:

Downloaded: 377 files, 52M in 12s (4.38 MB/s)
real    2m47.457s
user    0m0.433s
sys     0m5.828s

This corresponds to 443ms/page (=167 seconds / 377 pages).

Single Processor, single wget, --level=2

On a single processor quad-core server with ]po[ V3.5.0 "native" and parameters: user_id=8264 and --level=2:

Downloaded: 6044 files, 348M in 1m 15s (4.63 MB/s)
real    48m50.512s
user    0m6.909s
sys     0m53.950s

This corresponds to 484ms/page (=2930 seconds / 6044 pages).

Single Processor, 5x wget, --level=1

On a single processor quad-core server with ]po[ V3.5.0 "native" and parameters: user_id=8264 and --level=1:

The 5x wget results in 577ms/page (= 1107 seconds total runtime / 1885 pages).

This result can be interpreted as a nice scaling behaviour of the 4 cores of the server.

Part of the good scaling behaviour may be due to caching effects by ]po[ application layer and by the database.