Are you sure that the async version actually had applied all writes to the index in the measured interval? On Apr 11, 2013 8:13 PM, "Ales Justin" <ales.jus...@gmail.com> wrote:
> Although this change fixes query lookup, > it adds horrible performance: > > Running CapeDwarf cluster QueryTest: > > with HSEARCH-1296 > > 21:00:27,188 INFO > [org.hibernate.search.indexes.impl.DirectoryBasedIndexManager] > (http-/192.168.1.102:8080-1) HSEARCH000168: Serialization service Avro > SerializationProvider v1.0 being used for index > 'default_capedwarf-test__com.google.appengine.api.datastore.Entity' > 21:01:17,911 INFO [org.jboss.web] (ServerService Thread Pool -- 49) > JBAS018224: Unregister web context: /capedwarf-tests > > 50sec > > old 4.2.0.Final HS > > 21:08:19,988 INFO > [org.hibernate.search.indexes.impl.DirectoryBasedIndexManager] > (http-/192.168.1.102:8080-2) HSEARCH000168: Serialization service Avro > SerializationProvider v1.0 being used for index > 'default_capedwarf-test__com.google.appengine.api.datastore.Entity' > 21:08:20,829 INFO [org.jboss.web] (ServerService Thread Pool -- 49) > JBAS018224: Unregister web context: /capedwarf-tests > > 841ms > > --- > > I added > > <property name="enable_bundling">true</property> > > to AS jgroups transport config, but no improvement. > > Any (other) idea? > > -Ales > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev