[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513?pag...
]
Sanne Grinovero commented on HSEARCH-513:
-----------------------------------------
I just pushed a very experimental new optimization engine to process the Work list to GIT
https://github.com/Sanne/hibernate-search/tree/HSEARCH-513
Using your benchmarks it's already way faster, still it's missing the main
optimization yet which is to cap the recursion for @ContainedIn according to
@IndexedEmbedded.depth - that's coming next, but you could give it a try already,
it's in the branch named HSEARCH-513.
I expect a 20X performance improvement on the version currently in github when using your
provided tests, please confirm. It's definitely going to improve more as soon as I
figure out the best way to find the inverse-depth parameter to use.
Experiencing long delays when indexing entities saved in different
transactions
-------------------------------------------------------------------------------
Key: HSEARCH-513
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 3.2.0.CR1
Environment: Hibernate 3.5.1-Final
Spring 3.0.2
MySQL Connector 5.1.6
Reporter: Florin Haizea
Assignee: Sanne Grinovero
Fix For: 3.3.0.CR1
Attachments: AllLibsExceptSpringAndHibernate.zip, build.xml,
GedcomManagerTests-2010-11-24-shutdown-1.zip, hibernate-search-jms.zip, hibernate3.jar,
HibernateSearchJira.zip, MavenIndexingTest.zip, output.txt, output08052010.rtf,
SpringAndHibernateLibs.zip
https://forum.hibernate.org/viewtopic.php?f=9&t=1003224
I have 3 entities Person, Event and ParentOfBirthEvent. I save about 8000 Person objects
in batches of 20, each batch is being saved in a different transaction. After a sufficient
number of entities have been persisted (the saving and indexing of initial batches takes
between150ms and 500ms) the indexing of the entities that are saved in some of the
following batches takes a very large amount of time (sometime even minutes for a whole
batch).
The problem is that in order for these delays to appear there has to be a certain
relationship between the objects saved in the current batch and objects saved in previous
batches. The only way in which I can reproduce this 100% is by importing a file (which was
submitted by one of the users of our app), creating entities based on the data in that
file and saving the entities in batches of 20. When I reach batch number 273 or so the
indexing starts taking a lot of time.
If I removed the @IndexedEmbedded annotation from the "parent" field in the
ParentOfBirthEvent class the problem is solved. Also, if I removed all the hibernate
search listeners from the sessionFactory the problem is solved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira