A Comparison of Public Proxy Software using Wisconsin Proxy Benchmark
Jin Zhang and Pei Cao
University of Wisconsin-Madison
list of available proxy software, we downloaded and tried to install
all the publicly available proxy software. Here is a report of our experience.
We also conducted a preliminary test of the software using a small
configuration of the Wisconsin Proxy Benchmark. We report our results here.
You should read Duane's
brief description of the proxy software first, and then read this document.
This document includes our understand of the proxy architecture and our
experience with installing them and testing them.
Note: the benchmark results reported here are very preliminary, and
should not be considered as any significant indication of the proxy's performance.
The configuration of the benchmark is described here.
For each proxy, we listed blow:
architecture of the system: process based, thread based or even driven
installation experience: how to install the software, easy or not
configuration experience: how to configure the system. Basically, there
are three different ways to configure the proxy:
using a configuration file, user manually edit the configuration file
using a web based configuration interface
using the command line arguments
limitation: the limitation we observed about the proxy
architecture: process based, fork
one process on each request
installation: run make
see Squid and Netcache
architecuture: single process, event-driven
simple, just "make install"
architecture: process based proxy,
fork one process on each request
simple, may need to change a little bit of Makefile before running make
quite a lot of command line options
can not specify the cache size
commercial product; runs on WinNT only; rumors is that
it will come free with WinNT 5.0;
architecture: process based,
simple, run configure and make
can not run without caching
commercial product; runs on Novell's own operating system;
in other words, software/OS integrated;
architecture: process based
architecture: thread based, pre-fork threads
installation: simple, run
java install to install
uses web-based interface for configuration. But need to learn much about
the system architecture before knowing how to configure.
proxy returns "HTTP/1.1 200" even if the original server returns
commercial product; not available to us.
commercial product; the current beta doesn't run on Solaris. New beta out
around July 7th.
architecture: thread based
simple, runs configure, make install, install
web-based configuration interface. Need some time to figure out, but not
when the server replies with "Expires:" header, the proxy does not
cache the document.
commercial product; runs only on Windows NT.
architecture: thread based, create
a new thread on each request.
with bytecode, no installation needed after unpack the package
configuration file, need to know a little bit about system architecuture
the modules of the system.
Commercial product; software/OS integrated; comes as a box;
Commercial product; new versions will have software/OS integrated. Not
available to us.
Commercial product. Comes as a software-only product and a software/OS
combined product. We have not been able to obtain an evaluation version.
IBM Web Traffic Express
Commercial product. We got an evaluation version off the Web, but can't
install it on our Solaris machine. The Web page on installation apparently
only address installation on WinNT. We simply can't figure out how to install
it. IBM was no help on this.
Performs image compression and caching. Commercial product. Only available
through ISPs using it. Intel claims that about three ISPs are using this
Commercial product. Evaluation version not available to us.
"Packetstorm Technologies sells a caching appliance called WebSpeed
which runs Squid and is configured for transparent caching. "