Re: Lots of EOs slow down the performance
Re: Lots of EOs slow down the performance
- Subject: Re: Lots of EOs slow down the performance
- From: "Yung-Luen Lan" <email@hidden>
- Date: Thu, 6 Nov 2008 17:05:08 +0800
Ah, thanks to all.
First thing I tried is AjaxLongResponse. I thought it's acceptable to
display a progress bar and let users wait. Surprisingly, I still got a
"no instance error" after 150,000 eo created.
I then tried the suggestion to replace CSV component with a library
that dump the data into files. Nothing changed. I got the csv
component wrong. It's not slow to use component.
Investigation more, actually, it's slow to do ec.saveChanges() with
150,000 eo inserted. I got broken pipe. I got heap memory error. I
have no idea why it break AjaxLongResponse. It's in another thread,
isn't it?
Anyway, I do ec.saveChanges() each 1000-iteration of eo insertion, and it works.
Just curious how do you deal with editingContext.saveChanges() with
lots of EO inserted? Um, I don't think 150,000 should be a big deal in
21 century.
Regards,
yllan
On Wed, Nov 5, 2008 at 10:45 PM, Guido Neitzer <email@hidden> wrote:
> On 05.11.2008, at 02:56, Yung-Luen Lan wrote:
>
>> How could I improve the performance? Or at least let my page won't be
>> killed after 30 secs.
>
> 1. Use raw rows.
>
> 2. Don't use a component, dump for example into a file and deliver the file.
>
> 3. Use WOLongResponsePage or something similar (ERXLongResponseTask,
> AjaxLongResponse) to create the file in the background.
>
> 4. Use Wonder to make all of that way easier.
>
> 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