Re: HOWTO: Speeding up Spyce/CGI

Jonathan Ellis wrote:
> Your solution sounds like it was interesting to write!  cgiproxy sounds
> cool.

Pretty brain-dead actually, just grab the env vars and spit out some
http headers. But it's a hell of a lot faster than plain CGI.

> 
> But I'm having a hard time thinking of a good reason to actually deploy
> this.  For development, obviously just use the Spyce server on your
> local machine.  For production, a VPS from someone like westhost is so
> cheap -- you can usefully run Spyce for $7/month -- that I don't see
> saving another few dollars in exchange for "the service may be down
> randomly until cron restarts it, and if it gets popular, that will be
> increasingly often" as being worth it.

Point 1 - all the $7 VPS hosts I've seen have a strict limit on number
of domains, so if you've got several web clients, the $7 quickly turns
into $14, ... $35 ...

Point 2 - I'm doing websites for several niche-market small businesses,
which will have fairly modest traffic. Since I have one Spyce process
per site, it'll likely be weeks between each <60s outage.

Point 3 - if a website gets so popular that the 30-CPU-seconds trigger
kicks in often and forces frequent cron'ed restarts, then *that* is the
appropriate time to switch to a fancy VPS with generous multi-domain
support.

> I hope you stay enthusiastic about Spyce now that I've rained on your
> parade. :)

I've had worse :)

Now I've just gotta learn Spyce properly and avoid forming bad habits
along the way.

-- 
Kind regards
David


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642