[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513?pag...
]
Florin Haizea commented on HSEARCH-513:
---------------------------------------
Hi Amin,
Today I tried to see why your project has such good insert times per batch and mine
doesn't. Well, first I am using a FSDirectoryProvider and you are using a
RAMDirectoryProvider. This causes all of your batch insert times to be 4-5 times faster
than mine (this is just an estimate, didn't look much into this). But this still
doesn't solve my issue, namely that some of the batches take a very long time to be
saved. Even using the RAMDirectoryProvider.
What does make a difference though are the equals/hashCode methods in the Person, Event
and ParentOfEvent classes. If I comment those out in your project, I can reproduce the
long insert times (the first one being for batch 273). Similarly, if I implement the
equals/hashCode in my project, I do not experience those long times. So overriding
equals/hashCode for the indexed entities seems to solve the problem.
Is this a bug? Must we override equals/hashCode in all our indexed entities? Not that this
is a problem, just that I didn't know it was that important.
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
Fix For: 3.3.0
Attachments: AllLibsExceptSpringAndHibernate.zip, build.xml,
hibernate-search-jms.zip, hibernate3.jar, HibernateSearchJira.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