Re: Designing Batch List entries
Re: Designing Batch List entries
- Subject: Re: Designing Batch List entries
- From: Guido Neitzer <email@hidden>
- Date: Fri, 23 Mar 2007 22:49:24 -0600
On 23.03.2007, at 13:53, Ted Archibald wrote:
From my testing, if you created 200-500 empty Payment EOs, the app
takes a substantial amount of time to set each object up in memory.
If you create them only in memory, it should be pretty fast. If you
write them to the database, make sure, you write in batches to the
database and don't call saveChanges() after every creation.
I am able to insert a couple of thousand more or less simple records
per second to the database on my notebook which is normally limited
by the slow harddrive, so creating 500 objects in memory shouldn't be
a deal at all ... But nevertheless you should be careful with memory
usage.
The other thing is, that you have to make sure, that the executed SQL
is not the performance bottleneck (hints: batch faulting, too many
roundtrips, inefficient roundtrips). Turn on SQL logging, check
whether there's a problem. Log the exact time you need to create the
objects in memory (are they really in memory or are they written to
the db?) and see where the bottleneck is.D
cug
_______________________________________________
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