Re: Newbie: Mixing HTML & WO Pages?
Re: Newbie: Mixing HTML & WO Pages?
- Subject: Re: Newbie: Mixing HTML & WO Pages?
- From: email@hidden
- Date: Thu, 23 Oct 2003 13:24:30 CDT
- Priority: 3 (Normal)
[demime could not interpret encoding binary - treating as plain text]
On Thu, 23 Oct 2003 19:56:40 +0200 petite_abeille wrote:
> On Thursday, Oct 23, 2003, at 19:14 Europe/Amsterdam, Bob McCormick
> wrote:
> makes your life easier... and in the grand scheme of things... EOF
> doesn't add much overhead if you take into account the entire
> request/response loop...
Personally, I have not found this to be true. Back when I switched from
ColdFusion to WO, re-implementing an app in WO that had been in CF....
db access was much slower. Mainly when fetching, is what I remember
paying attention to. Using all the EOF performance tuning tricks in the
book can help (pre-fetching, batch faulting, etc), but in the end, I
think it's just due to the time it takes to instantiate a Java object and
there's not much to be done. For every row you fetch, there are
potentially a bunch of EOF objects instantiated, including the object for
the EO itself as well as a snapshot and others.
Fetching a few hundred objects, significantly slower in WO than CF. CF,
at least a few years ago when I was using it, was actually astoundingly
fast. WO (again, at least a few years ago when I was doing this
transition), much slower. Noticeable to the user---from a click in CF
resulting in a blindingly fast page generation, to a click in WO
resulting in a second or more for the page to be returned.
Of course, you could say: re-design your app so you never need to fetch a
few hundred objects. But that's besides the point.
And yeah, I'm still using WO. I couldn't possibly have done what I've
since done in WO using CF, it just wouldn't have been feasible. So it
doesn't matter that CF was faster, CF woulln't have worked.
>
> In any case, here is an handy diagram for your perusal which
> illustrates what's happening when fetching data through EOF:
>
> http://developer.apple.com/documentation/WebObjects/Enterprise_Objects/
> Fetching/index.html
>
> > This particular project isn't going to have to worry about past
> > projects performance metrics, but a future project might. Do you (or
> > any lurkers) have thoughts on performance difference? Sorry if I'm
> > coming across paranoid, I just really wish to understand the
> > real-world performance of WO so that I can plan or design >
> accordingly.
>
> The bottom line as far as "performances" goes is that if you have a
> sane design in the first place everything else will follow. But this
> has nothing much to do with EOF in and by itself. Obviously you
> shouldn't fight whatever toolkit you may choose to use [1], but that's
> a secondary issue.
>
> Cheers,
>
> PA.
>
> [1]
> http://www.pragmaticprogrammer.com/developers/ppllc/papers/1998_04.html
> _______________________________________________
> webobjects-dev mailing list | email@hidden
> Help/Unsubscribe/Archives:
> http://www.lists.apple.com/mailman/listinfo/webobjects-dev
> Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.