Re: EO Caching
Re: EO Caching
- Subject: Re: EO Caching
- From: Chuck Hill <email@hidden>
- Date: Mon, 10 Dec 2007 10:06:19 -0800
On Dec 10, 2007, at 7:16 AM, Mike Schrag wrote:
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?
What Mike said. Jumping to conclusions is very ineffective
optimization technique. Measure. Log. Investigate. First
determine why it is slow. Look at the database. Can you add indexes
to make it faster? Will a different schema address the performance
problem. Then look at EOF and see if there are built in ways to
handle this, batch faulting is one such example. Failing that, look
at what can be done in code.
Chuck
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@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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