Remember, it is not only the amount and size of the logical logs that
determines the amount of records you can load (the size of a
transaction). You must keep in mind the other jobs also running while
you do the load; they also make use of the logs. That is maybe why you
every time gets a different count.
David Reed
-----Original Message-----
From: informix-list-bounces@iiug.org
[mailto:informix-list-bounces@iiug.org] On Behalf Of John Carlson
Sent: Thursday, February 09, 2006 05:34 AM
To: informix-list@iiug.org
Subject: Re: dbload vs. load
On 8 Feb 2006 00:58:40 -0800, "christrier" <chrishunnell@gmail.com>
wrote:
>
> > Is bullshit 'ClownSpeak' for RTFM?
>I have read the fu*** manual that is why i tried to insert the data
>with the load from statement.
>In the Manual there is a page with 4 questions about choosing the right
>import-utility. I had to answer those questions in that manner that i
>had choosing load as my result....
>
>> IIRC, each operation (in this case, each INSERT) has to check or
validate
>> something in the log, and does this in a relatively inefficient
manner --
>> traversing a linked list. So the longer the transaction gets, the
slower
>> each subsequent operation is. When the transaction is short, the cost
of
>> committing is relatively high, but when the transaction gets longer,
it
>> can often be substantially better to commit more often (if this is
>> possible).
>
>I guess it is better to commit more often and therefore i have another
>question: i have tried many values for the commit-intervall and i never
>really found out what the max-value was. I tried with 10.000 and it
>didn't workout. I have informix sql version 9.40
You're trying to find the max value for commit interval? Seems that
would depend on how much logical log space you have . . . . .
JWC
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list