Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was wondering which class would be more efficient: PHP (Glype, PHProxy), CGI (CGIProxy), or javascript based scripts that run on a webserver, or an http proxy run through squid. Assuming neither class was doing any caching, would one or the other be much more efficient at handling web browsing?


share|improve this question
up vote 1 down vote accepted

It sort of depends on how you integrate these into your server farm.

CGIProxy is a Perl app. PHPProxy is PHP, of course.

If, for example, you're running MOD_PERL then my vote is for CGIProxy.

Having extensive experience with Squid, you need a lot of RAM to make Squid really perform well.

PHPProxy would be my 2nd choice... (or first choice if not running MOD_PERL). PHP plugin is faster than forking a perl interpreter that is not built as an apache module (mod_perl). However, mod_perl apache module appears to be faster than php plugin.

share|improve this answer

Surely SQUID would be fastest. Its a native application while the script based solutions are interpreted. SQUID needs a fair amount of memory but is that an issue on a modern server?

I've used the Windows port of SQUID extensively and I find it to be excellent, though somewhat involved to configure.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.