Re: how to thread a really computationally intensive page ?
Re: how to thread a really computationally intensive page ?
- Subject: Re: how to thread a really computationally intensive page ?
- From: Gavin Eadie <email@hidden>
- Date: Thu, 27 Mar 2008 16:46:52 -0400
On Mar 27, 2008, at 3:57 PM, Mike Schrag wrote:
Are you sure it is not firing faults, one by one by one...
Yeah, 10:1 this is horrible faulting behavior ...
I just talked to my buddy and he notes that there is some db access in
this component after all.
Six years ago, our team were all WONovices, and one of our colleagues
thought he'd 'improve' EOF by adding a smart layer over it. EOF is
more than plenty smart all by itself and I expect this other stuff and
EOF are operating at cross-purposes [for example, as you suggest, it
may be defeating EOF's faulting strategy and slowing everything
down]. The db has grown over time (university phone records) and any
db inefficiency is probably going up faster than linearly. I've been
trying to eliminate his code, but it got knotted around a lot of stuff
in a rather non object oriented manner.
I must admit it wasn't till I saw just how fast the parser was ripping
through my time-wasting HTML that I started to realize there had to be
more going on than just rendering effort. A million <wo:loops> per
second caught my attention!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden