Subject Re: [ib-support] Re: Massive INSERT test
Author Svein Erling Tysvaer
At 14:06 11.02.2003 +0000, you wrote:
>This is my embedded SQL statement:
>INSERT INTO myDB (myCols ... ) VALUES( ... )
>Not sure if it answers your question.

Nor am I :^)

I do not use embedded SQL at all, but what I generally find the best thing
to do is to have a statement like

INSERT INTO myDB (myCol1, myCol2...) VALUES (:Param1, :Param2)

prepare it once, and then fill in parameters and call execute for every
row. Around every 10,000 or 20,000 I would call commit.

> >2,000,000 0:53 sec
> >2,900,000 4:47
> >
> >ibserver.exe used 40 MB memory at that point.
> >
> >I stopped the test and restarted the service.
> >
> >3,000,000 1:28
> >3,300,000 2:14
> >ibserver.exe is up to 10 MB memory usage at this time.

Well, something certainly doesn't seem right, but as I said I do not use
embedded SQL so I cannot help you with that. Or maybe, could there be a
problem with the database having to make too many backup versions? What is
the gap between the Oldest Active Transaction and Next Transaction at the
various times of your run?