There are several reasons for which indexing all root types in parallel turns out to be a bad idea.
number of needed jdbc connections is unpredictable
some other operations could run in parallel (index optimisation for eg)
generates a very high amount of contention without a clear benefit
Discussed on http://lists.jboss.org/pipermail/hibernate-dev/2013-August/010229.html and related to
Yes, it's a local PostgreSQL database. I'm running it with your suggested configuration and I can confirm that the CPU are used at 100%, which is what I had with 3 indexing threads and my original configuration.
Are we OK with the API, especially the name of the fluid setter? If so, I'm planning to update the paragraph "6.3.2. Using a MassIndexer" of the documentation.
Sanne, with your settings, indexing took 10 minutes. Looks like I should change my default configuration .
won the bet
I changed the method name and updated the documentation. If everything is OK for you, I can rebase and rewrite the history of my branch to obtain a clean commit before you merge.
Thanks for your feedback.
Thanks! looks like perfect, merging.