[Hibernate] Re: slow performance on flush

[Gavin K. <ga...@ap...>]

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 -----=20
  From: Christoph Sturm=20
  To: hib...@li... ; Gavin King=20
  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=3D1;j<100;j++)
  {
      for (i=3D1;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