Re: EOModeler and more
Re: EOModeler and more
- Subject: Re: EOModeler and more
- From: Arturo Pérez <email@hidden>
- Date: Sun, 11 Jan 2004 23:14:52 -0500
On Jan 11, 2004, at 10:47 PM, james cicenia wrote:
If I have thousand of users why should I instantiate full complete
objects for a screen that needs
only to show a small bit of information. In addition, the full objects
will contain a lot of attributes
of type Text. This could be very expensive performance wise.
Why should you be fetching thousands of users? Or are you saying that
thousands of users would
be using your application? I thought we were talking about a screen
that needed to show open projects
by department? Surely you don't work in a company that has thousands
of departments? Or does your
company run thousands of open projects simultaneously?
In any case, thousands of users may be viewing a page that displays two
dozen objects. If you fully
utilize EOF object caching then you will hit the database once no
matter how many times the page is
displayed. Your implementation will hit the database every time the
page is displayed. Which is
more expensive?
As an FYI, our portal was featured on the CBS morning show (whatever
it's called). We didn't know
and we didn't do the above level of optimization before it happened;
i.e. we instantiated full
objects for EVERYTHING. The portal continued to function just fine
when the tens of thousands
of CBS morning show watchers fired up their browsers.
----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
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.