Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add the ability to set the number of different root types indexed in parallel

Description

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 https://hibernate.atlassian.net/browse/HSEARCH-598#icft=HSEARCH-598

Activity

Sanne GrinoveroAugust 12, 2013 at 2:17 PM

Thanks! looks like perfect, merging.

Guillaume SmetAugust 12, 2013 at 12:59 PM

Sanne,

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.

–
Guillaume

Sanne GrinoveroAugust 6, 2013 at 4:08 PM

won the bet slightly smiling face

Guillaume SmetAugust 6, 2013 at 3:50 PM

Sanne, with your settings, indexing took 10 minutes. Looks like I should change my default configuration slightly smiling face.

Guillaume SmetAugust 6, 2013 at 1:25 PM

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.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created August 5, 2013 at 4:44 PM
Updated October 14, 2013 at 11:53 AM
Resolved August 12, 2013 at 2:18 PM

Flag notifications