Comments on: A Grails Memory Leak

By: Tweets that mention An Army of Solipsists -- Topsy.com

Tweets that mention An Army of Solipsists -- Topsy.com — Thu, 21 Jan 2010 01:20:14 +0000

[...] This post was mentioned on Twitter by Ryuichi Ohtaki, ふむふむ. ふむふむ said: RT rohtaki: A Grails Memory Leak http://bit.ly/8Mbpwy なるほど。これでバッチ処理でメモリーリークするわけだ。 [...]

By: Burt

Burt — Fri, 06 Nov 2009 19:09:28 +0000

Mark -
Typically when doing batch imports in Hibernate you flush and clear the session regularly, e.g. every 25 or 100 inserts or so. I put the call to clear PROPERTY_INSTANCE_MAP in there, e.g.:

for (int i = 0; i < count; i++) {
  new Thing(...).save()
  if (i > 0 && i % BATCH_SIZE == 0) {
    session.flush()
    session.clear()
    DomainClassGrailsPlugin.PROPERTY_INSTANCE_MAP.get().clear()
  }
}

but you could also call it after every save() since as long as that’s successful you no longer need the associated errors.

By: Mark O'Brien

Mark O'Brien — Fri, 06 Nov 2009 13:06:10 +0000

Hi Burt,

Where does this piece of code:
DomainClassGrailsPlugin.PROPERTY_INSTANCE_MAP.get().clear()

need to go…is it related to every domain class access?

Thanks
M

By: Ted Naleid » Batch Import Performance with Grails and MySQL

Ted Naleid » Batch Import Performance with Grails and MySQL — Thu, 01 Oct 2009 05:54:08 +0000

[...] reading through a couple of very helpful posts by Burt Beckwith, and reading through the Hibernate chapter on batch processing, we have all [...]

By: Ted Naleid

Ted Naleid — Sat, 12 Sep 2009 20:08:32 +0000

Thanks Burt, this post was a big help in figuring out what was going on with some batch loading I’m doing through GORM. I wish I had found it a couple of days ago .