On Sun, 20 Jul 2003, Dave Rolsky wrote:

> Actually, H::T is almost certainly _much_ faster and less RAM-intensive
> than Mason, at least when you measure the time it takes to serve a single
> page/component.  OTOH, if you were to try to replicate some of Mason's
> more powerful features with H::T, like autohandlers, inheritance, etc.,
> then I'm sure that'd bring H::T's speed down to Mason's level ;)

Fair enough. I haven't actually deployed anything under H::T. I've
played with it, and some of it I like. I have stolen part of it for
deployment, but it ended up really mangled and site specific, so that
doesn't count.

Mason isn't fast. It is, however, fast enough for high volume sites -
that I will assert.

From my view, the utility of autohandlers and dhandlers, in terms of
code written vs. cost and time, is an enormous win. Add to that the
flexibility between library developmers and HTML coders, in that there's
a constant feedback loop that enforces reasonable development and
interaction to ensure that all roles are working for the same goal.

And in general, I don't care about RAM. A 1G server is cheap. Tune
apache properly and you have no problems for sites approaching .25M
visits/day. If you need to exceed that, you need multiple front-end
boxes. But if you're doing that amount of traffic, you probably need
redundancy anyway, so the issue is moot.

> In other words, you generally get what you pay for.  The most powerful and
> flexible systems are generally slower and more RAM-hungry.  One exception
> to this might be Embperl, which has large chunks written in C.  In that
> case, the cost is paid for in development time.

Agreed. 

In general, I love Mason, but still do write mod_perl interfaces for
some things, when performance is important. For that matter, I push a
lot of work onto the database, and then write C extensions to it to
handle specific performance problems. Apache, perl, mason, postgres is a
kickass combination, where you can fix almost any problem, quickly and
cheaply. As usual, this pushes back at the developer, who is obligated
to make the right choice. It is certainly not the only choice, but it is
the right one(tm) for me.

Again, I'm offering opinion, based on my particular experiences. Nothing
more, nothing less.

-j, who used to run custom NSAPI modules talking to Oracle under NES under 
high loads, and is an unabashed fan of mod_perl. <shudder>



-- 
Jamie Lawrence                                        [EMAIL PROTECTED]
"People should be allowed to keep midgets as pets."
    - Gov. Jesse Ventura


Reply via email to