Databases
StackOverflow2013
Postsdbo
POReducing memory usage for batch JDO inserts
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReducing memory usage for batch JDO inserts
    primarykey
    data
    text
    <p>We have a Java web app using Data Nucleus 1.1.4 / JDO 2.3 for persistence.</p> <p>There's a batch import operation that persists a large number of JDO objects in one shot. We've had some situations where OutOfMemoryError's are being thrown because the data to import is so large. </p> <p>The intended pattern was to loop through the input stream, parse a row, instantiate a JDO object, call makePersistent, then release the object reference to the JDO object in order to keep our memory footprint flat regardless of the input data size. </p> <p>In doing some analysis of the heap during this operation, it appears that the JDO object instances pile up and take up a large chunk of memory until the <code>commit</code> happens. Even though we don't hold references to them it looks like Data Nucleus's <code>PersistenceManager</code> and <code>Transaction</code> implementations reference an <code>org.datanucleus.ObjectManagerImpl</code> object that holds onto a list of "dirty" JDO object instances (actually copies of the original). There's probably a good rationale reason for this but I was a bit surprised that the framework needed to hold onto copies of each JDO object. They are let go after the commit, but given that we want to make sure all insertions happen atomically, we need to run this operation inside of a transaction. In it's current state the memory usage is linearly correlated to the data input size which opens us up for these OutOfMemoryErrors - if not for a single operation, then under concurrent operations.</p> <p>Are there any tips or best practices around keeping as close to a flat memory footprint for a batch JDO insertion operation like this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMarplesoft
    1. USMarplesoft
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POReducing memory usage for batch JDO inserts
      1. USMarplesoft
      1. VTFavorite
    1. COI'm not sure how to solve this but I'm believe stating your persistence-configuration properties file contents would really help.
      singulars
      1. POReducing memory usage for batch JDO inserts
      1. USMuhammad Gelbana
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload