I don't think so.  That was my original point: who cares how efficient CF's
generated Java is?

If you're very concerned about performance, you might consider switching to
another platform, but I'm pretty confident that you can get good enough
performance out of CF if you handle your DB interactions efficiently, and
cache data appropriately.

Here's a REMARKABLY contrived example, but it illustrates the point.

Say JSP is 20% faster than CF.  That's pulled from a hat, by the way.
You've got a CF request that's 500ms to execute.  200 is DB queries (same
for both platforms, basically), so 300ms of actual processing.  JSP will
give you 240ms, a 12% overall savings.

Now we optimise the queries so that 200ms drops down to 120ms.  That'll drop
the overall request time by 16% for CF and 18% on JSP.

Now lets cache.  We get to cut out some queries (probably not all of them
though), so we'll have a optimized DB time of say 20ms.  We also get to do
some caching of generated content, so we can trim that processing time down
to say 50ms, for a total of 70ms on CF.  Now the 20% JSP improvement (pulled
from a hat, I remind you), is really only worth 10ms per request.

So optimizing the DB and caching gives a 84% reduction in request time.  If
you add the 20% improvement you'd get from converting to JSP, you'll bump it
up a whopping 4% to a 88% reduction.  Not very good ROI, in my book.

Cheers,
barneyb

> -----Original Message-----
> From: Calvin Ward [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 29, 2004 10:49 AM
> To: CF-Talk
> Subject: RE: How does CF generated Java bytecode compare with
> Native Java ytecode
>
> ahhh, but is it a significant difference?
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to