Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The ID generation strategy is critical for batch insertion in Hibernate. In particular, IDENTITY generation will usually <strong>not</strong> work (note that AUTO typically maps to IDENTITY as well). This is because during batch insert Hibernate has a flag called "requiresImmediateIdAccess" that says whether or not generated IDs are immediately required or not; if so, batch processing is disabled.</p> <p>You can easily spot this in the DEBUG-level logs when it says "executing identity-insert immediately" - this means it has skipped batch processing because it was told that generated IDs are required immediately after insertion.</p> <p>Generation strategies that typically <strong>do</strong> work are TABLE and SEQUENCE, because Hibernate can pre-generate the IDs, thereby allowing for batch insertion.</p> <p>A quick way to spot whether your batch insertion works is to activate DEBUG-level logs as BatchingBatcher will explicitly tell you the batch size it's executing ("Executing batch size: " + batchSize ).</p> <p>Additionally, the following properties are important for achieving batch insertion. I daren't say they're required as I'm not enough of a Hibernate-expert to do so - perhaps it's just my particular configuration - but in my experience they were needed nonetheless:</p> <pre><code>hibernate.order_inserts = true hibernate.order_updates = true </code></pre> <p>These properties are pretty poorly documented, but I believe what they did was enable for the SQL INSERT and UPDATE statements to be properly grouped for batch execution; I think this might be the multi-row inserts you're after. Don't shoot me if I'm wrong on this, I'm recalling from memory.</p> <p>I'll also go ahead and assume that you set the following property; if not, this should serve as a reminder:</p> <pre><code>hibernate.jdbc.batch_size = xx </code></pre> <p>Where xx is your desired batch size, naturally.</p>
    singulars
    1. This table or related slice is empty.
    1. POHibernate Relationship Mapping/Speed up batch inserts
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USvoetsjoeba
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@JDR: Thank you very much for all this info- I am in the process of changing my ID generation to native (will this disable batching as well?), and will add your other ideas. I already have jdbc.batch_size = 50 but don't have order_inserts/updates. I'll let you know how well it works.
      singulars
      1. PO
      1. USashurexm
    2. CO@JDR: I implemented your suggestions and I can see that it is grouping together my inserts so all the tables are getting inserted in order. It is inserting ALL the Test, then ALL etc.. It is showing me that the batch size is 50- which is good. But I'm still getting roughly the same performance I was getting before- which is approximately 5 minutes for 3300 records (keep in mind, each record means an one insert into 5 different table).
      singulars
      1. PO
      1. USashurexm
    3. CO@manyxcxi: Changing the IDs to native disabled batching for me due to the requiresImmediateIdAccess variable (using H2 and Hibernate 3.5.1-Final). If the batcher says that it's performing batches of 50 then that's pretty much what it's doing, it's sort of the goal here. Five minutes for 3300 records seems a bit excessive, I can insert 1000 records in about a second with even some additional Hibernate Search overhead (albeit on an embedded H2 database). Do you have some sample output logs anywhere I can look at? What database are you running and what connection pool are you using?
      singulars
      1. PO
      1. USvoetsjoeba
 

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