A commit will be done every 1000 inserts. Also, there are not
differences in doing that with ibatis and "plain jdbc-statements". Both
will do the same, but ibatis needs twice the time.
Larry Meadors schrieb:
> ...and if you do batch it, you may still want to commit after ever
> 100-200 inserts to keep the database from creating a massive rollback
> segment.
>
> Also, if you are inserting 100,000 rows, you may want to look into
> using a native data loader tool. It'll be WAAY faster.
>
> Larry
>
>
> On 9/1/06, Chris Lamey <clamey@localmatters.com> wrote:
>> Are you batching the inserts? If not, then a commit is done after each
>> insert, which is very slow.
>>
>> On Fri, 2006-09-01 at 14:21 +0200, Ralf Assmann wrote:
>> > Hi there,
>> >
>> > making a performance test with ibatis, we got a very slow runtime.
>> > Inserting 100000 rows into a table, we took more than twice the time
>> > than using own-written prepared statements. The time was definitely
>> > lost during the transaction time writing the data to the database,
>> > calling sqlMap.insert(...).
>> >
>> > Does anyone know if this runtime is normal while using ibatis or is
>> > there any xml-parameter to optimize it?
>> >
>> > Many thanx,
>> >
>> >
>> > Ralf
>> >
>>
|