I would recommend taking a step back here and profile what's actually
going on ... What exactly is slow? Have you turned on SQL debug to see
if you're firing hundreds of faults? Is it just that you're getting a
lot of objects back? How many objects?
ms
On Dec 10, 2007, at 10:02 AM, Jeffrey Simpson wrote:
Thanks for the input.
I have decided that this whole course is wrong. We have some
performance
problems and my boss wanted to see if there was a magic bullet.
Loading the
whole database into memory at startup was not the way to go.
I think we need to go to raw rows for display only screens and only
make EO
objects when we are going to edit. I think this is the recommended
way to
go.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
