I'm using OGM 5.0.CR1 on Wildfly 10. I have a service that loads on app startup and persists a couple thousand entities. According to log output, it only takes a couple hundred milliseconds to persist all the entities. However, if I use a non-persistent Infinispan data store, there's about 4 minutes of time from when the loader service method completes and when the app goes to the "started" state. The more data I persist, the longer this period of time becomes. This doesn't happen if I switch to the "map" data store - the app goes to the started state right after loader service completes.

I assume that OGM and/or Lucene are doing a bunch of work on the data (transaction management, indexing, etc). But why does it take so long? Is there any way I can enable debugging output to get a better idea of what's going on?

Hi,

You can increase the logging to INFO or DEBUG (e.g. by specifying log4j.logger.org.hibernate=info in log4j.properties in case you are working with Log4j). 4 min definitely sounds too long for a couple of thousand inserts. Alternatively, if you can provide a small Maven project exposing this issue, I'll be happy to take a look.

Thanks!

--Gunnar

I've changed logging level to DEBUG. Here are my observations... I'm running in Wildfly 10 and my loader service is a transactional EJB method which should flush entities automatically. I am seeing the entities persisted. However, I only see more debugging output from Hibernate if I manually call entityManager.flush(), but nothing that indicates problems.

Also, debugging output ends just after my entity loader service completes. I'm still left with a 4 minute wait time before my app goes to the started state. During that time, I see no debugging output.

I tried switching to a redis data store. I see my entities get persisted in redis just fine, but the after-persistence wait time is over 5 minutes and I get a java.util.concurrent.TimeoutException. To see if it made a difference, I tried switching Lucene indexes to be in infinispan rather than file-based, but having some trouble with class loading.

My entity model is fairly complex with lots of associations, elementcollections of maps, etc. I'll try to disable some of these to see if I can spot a bottleneck. Any debugging tips you could give me would be appreciated.

What do you mean by "wait time before my app goes to the started state"? If your app isn't started, how are you inserting these entities? You hit an interesting problem and I'd love to help, but it's really hard without knowing more details. If you e.g. remote debug the app, maybe you can see any locks after the persist has happened? If you could isolate a small test case, we'll give it a look.

--Gunnar