> Tried now... seems to be visibly faster without batch updates :-)... but
> why?
What we might need to do here is have a hibernate.max_batch_size property to
ensure that the batch doesn't get too huge. Its possibe that your problem is
a result of queueing up 1000 statements in a single batch. Do
Gavin King wrote:
There are a couple of different issues in this:
[...]
Im also not sure why the inserts are slow. They shouldn't be. Have you tried
disabling batch updates hibernate.use_jdbc_batch=false?
Gavin
Tried now... seems to be visibly faster without batch updates :-)... but
why?
An
rhaps.
- Original Message -
From: "Andrea Aime" <[EMAIL PROTECTED]>
To: "Gavin King" <[EMAIL PROTECTED]>
Sent: Thursday, October 24, 2002 8:52 PM
Subject: Re: [Hibernate] Mass delete and insert performance problems
> Gavin King wrote:
>
> >There are a cou
There are a couple of different issues in this:
Hibernate does *not* (yet) do mass deletes. Usually we need to load an
object up before we delete it, in case it has
(1) Lifecycle callbacks
(2) toplevel collections
(3) cascading deletes
(4) references to other deleted objects which need to be nulli
