It would be nice with a better documentation of the MassIndexer's threadsToLoadObjects and threadsForSubsequentFetching I thought they where the total that the MassIndexer was going to use, but in fact it was pr. entity-class. This makes a difference when you are trying to index several entity classes at once because you probaly will run out of DB connections (I did)