Re: [Hibernate] Re: slow performance on flush

[Juozas B. <ba...@ce...>]

It is better to use some "native" API like "COPY" for long running import,
some RDBM's support imports without constaint
checks, SQL parsing ....  , and sometimes "long running import" becomes very
"short".

----- Original Message -----
From: "Christoph Sturm" <ch...@mc...>
To: "Gavin King" <ga...@ap...>
Cc: "hibernate list" <hib...@li...>
Sent: Monday, November 25, 2002 3:27 PM
Subject: [Hibernate] Re: slow performance on flush


I have a really long running import, and I want to write the records to the
db as they come in. Is it save to clear the entries Map after a flush? Or
would you recommend a different approach?


  ----- Original Message -----
  From: Gavin King
  To: Christoph Sturm
  Cc: hibernate list
  Sent: Monday, November 25, 2002 2:23 PM
  Subject: Re: slow performance on flush


  Yup, all entries are kept in the session cache until you close the
session. Why would you use this kind of code?? Just flush() once at the end
(outside the loop).
    ----- Original Message -----
    From: Christoph Sturm
    To: hib...@li... ; Gavin King
    Sent: Tuesday, November 26, 2002 12:18 AM
    Subject: slow performance on flush


    Hi all!

    I'm trying to increase the performance of this pseudocode:

    for (j=1;j<100;j++)
    {
        for (i=1;i<100;i++)
        {
            session.save(class)
        }
        session.flush();
        session.connection().commit();
    }


    Now my problem is that flush doesnt take a constant time, but every
invocation of flush takes more time than the last one, the more I flush the
slower it gets. To me it looks like hibernate keeps the references to the
flushed objects in the entries map, and doesnt remove them. Is there
anything I can do about it?

    regards
     chris