91 words

Issue #170 - Inefficient memory usage with very large transactions

BugVersion: 2.4.3Priority: NormalStatus: FixedReplies: 1
#1
2012-10-13 01:06

When a large transaction is committed, ObjectDB increases some internal structures, i.e. allocates more memory, but from that point the structures remain big and the memory is not released even if all the next transactions are small.

This problem was found during a heap analysis (see #9 in this forum thread), and was fixed in build 2.4.3_02, but the fix was removed later in build 2.4.3_03 because it caused other problems (#10, #11 in that forum thread).

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support
support's picture
Joined on 2010-05-03
User Post #1,292
#2
2012-10-13 19:23

Version 2.4.4 fixes this issue, hopefully without undesired side effects.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support
support's picture
Joined on 2010-05-03
User Post #1,295

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Attachments:
Maximum file size: 32 MB
Cancel