Re: WO Performance...
Re: WO Performance...
- Subject: Re: WO Performance...
- From: Chuck Hill <email@hidden>
- Date: Fri, 24 Oct 2003 11:15:40 -0700
- Organization: Global Village Consulting, Inc.
Hi,
Colin Clark wrote:
In terns of performance, I think you'll find it more appropriate to
worry about performance later on in the development cycle of your
application.
>
Yes, premature optimization bad. It is a great waste of resources
fixing problems that exist only in your imagination.
EOF can't possible know how intelligently fetch your
data without you providing that extra information. You do that by making
decisions about batch faulting, prefetching, and using raw row fetches
where required.
>
Another useful thing that I don't often see mentioned is plain, old
performance indexes. EOF provides indexes for what it knows that it
will fetch (primary keys for firing faults). However, it can't guess
what sort of fetch specs you might write. It is worth examining the
selects made to the database for slow operations and seeing if an
index or two might dramatically speed the results. While optimizing
problems, I've dropped response time to a tenth of the original by
judicious use of batch faulting and indexes. A dramatic improvement
from from very minor changes!
Chuck
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
Progress is the mother of all problems.
- G. K. Chesterton
_______________________________________________
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.