SWPS 4.0 and Squid
Last day we needed to come up with some quick data on how proxy 4.0
compares with Squid, for an internal requirement. Soon a couple of
facts became apparent - architecture-wise, proxy 4.0 is miles ahead
as compared to squid, not to mention stability, user friendliness,
simplicity, etc. But feature-wise, proxy 4.0 does not quite match
up to Squid.
|
SWPS 4.0
|
Squid
|
Architecture
|
Multithreaded, MultiProcess
|
Single
Process, Single threaded
|
Admin GUI
|
Yes
- Full fledged
|
No -
Manual config file editing needed
|
| Distributed Admin |
Yes
|
No
|
Installation
|
GUI
based as well as CLI
|
Only
CLI
|
Performance
|
Faster (As per internal tests)
|
|
Memory Usage
|
Lesser (Ideally)
|
|
Migration
|
Admin GUI support
|
CLI
|
LDAP
Authentication
|
Inbuilt
|
Available as Addon
|
Prefetching of pages
|
Inbuilt
|
Available as Addon
|
localized messages/OLH
|
Yes
|
No
|
URL
rewriting (redirectors)
|
Inbuilt
|
Available as Addon
|
SNMP
support
|
Yes
|
Yes,
but enabling/rebuilding needed
|
Authentication
|
Inbuilt
|
Relies on separate processes
|
Content Rewriting
|
Inbuilt
|
Available(?) as Addon
|
Log
Analysis
|
Inbuilt
|
Available as Addon
|
Open
Source
|
No
(Not Yet)
|
Yes
|
Event Scheduling
|
Yes
|
No
|
Multiple Instances on Same
Host
|
Easy
|
Tricky
|
It's by no means a comprehensive
one, and i admit that it's been a rush job. I have left out the
negative points due to two reasons - that's what the requirement
demanded, and, the negative list would mostly be a list of features
that Squid has and proxy 4.0 doesn't. Anyway.
Trackback URL: http://blogs.sun.com/motor/entry/swps_4.0_and_squid
