Google

Some benchmarks

These bencmarks were done just to get some idea of what peak performance / main bottlenecks were present in the ftp search server for some configurations. The numbers given are not 100 percent accurate.

Onyx configuration 1

  • 1 GB RAM available
  • 4 200 MHz CPUs available
  • Local disk access.
  • Single threaded process, no use of fork().
  • Suffix tables available.
  • ~150000 searches total
  • 2.23 searches/second
  • 23 searches/CPU second..
  • 700 MB active virtual memory at end of test run.
  • Bottleneck: Disk IO.
With all data locked in memory (need 1.8GB RAM), the CPU would probably be the bottleneck, and we would have about 23 searches/second. With a multithreaded server process, performance could be further enhanced by using more CPUs.

Onyx configuration 2

  • 1 GB RAM available
  • 4 200 MHz CPUs available
  • Local disk access.
  • Single threaded process, no use of fork().
  • <50 searches total
  • 0.16-0.25 searches/second.
  • 0.16-0.25 searches/CPU second
  • 110 MB active virtual memory at end of a search.
  • Bottleneck: CPU
Brute force with a fast CPU is not good enough.

Pentium 90 configuration

  • 64 MB RAM available
  • 1 P90 CPU available
  • 1 MS160SE card with 96 MB RAM
  • Local disk access (NCR53C815 SCSI controller)
  • Single threaded process, no use of fork()
  • ~75000 searches total
  • 1.14 searches/second
  • 8-10 searches/CPU second
  • 55 MB active virtual memory at end of test run
  • Bottleneck: Disk IO

ftpsearch.ntnu.no configuration

  • 64 MB RAM available
  • 1 Pentium 100MHz CPU available
  • 1 MS160SE card with 96 MB RAM
  • Local disk access (NCR 53C810 SCSI controller)
  • Single threaded process, no use of fork()
  • 35000-40000 daily searches.
  • 55000-60000 daily navigations.
  • 50 MB active virtual memory.
  • Bottleneck: Disk IO

Simple benchmark, comparing with a commercial system

Performed: Fri Jan 26 1996 / Sat Jan 27 1996
Only one search was made for each entry in this table. Actual response times may vary with the load on the servers
Server QueryType Query Elapsed timeNumber of hits/matches
ftpsearch.ntnu.no -s binutils-2.0 0.66 s 5 hits
archie.uninett.no -s binutils-2.0 210.17 s 1 hit
archie.sunet.se -s binutils-2.0 1.61 s 0 hits
archie.doc.ic.ac.uk -s binutils-2.0 15.56 s 0 hits
archie.funet.fi -s binutils-2.0 37.79 s 2 hits
ftpsearch.ntnu.no -Z gcc-2.4.0 2.86 s 10 matches
archie.uninett.no -Z gcc-2.4.0 130.44 s 8 matches
archie.sunet.se -Z gcc-2.4.0 1.46 s 8 matches
archie.doc.ic.ac.uk -Z gcc-2.4.0 36.56 s 2 matches
archie.funet.fi -Z gcc-2.4.0 10.79 s 9 matches
ftpsearch.ntnu.no -X ^gcc-[0-9]\.[0-9]\.[0-9]\.tar\.gz$ 0.22 s 23 matches
archie.sunet.se -X ^gcc-[0-9]\.[0-9]\.[0-9]\.tar\.gz$ 3.39 s 19 matches
ftpsearch.ntnu.no -X ^gcc-([0-9]\.)+tar\.gz$ 0.79 s 28 matches
archie.sunet.se -X ^gcc-([0-9]\.)+tar\.gz$ 3.36 s 0 matches
QueryType -s is case insensitive substring search
QueryType -Z is case insensitive substring match, i.e. only the file name is returned
QueryType -X is regular expression match.

[ FTP search | Search page | Technical info ]


tegge@idt.ntnu.no
Last modified: Thu Sep 19 00:00:14 MET DST 1996