I think we need more fine-grained config for this new JGroups sync feature.
I added this to our cache config
<property
name="hibernate.search.default.worker.execution">async</property>
and it broke our tests.
Where previous (old / non JGroups sync) behavior worked.
It of course also works without this async config,
but in this case we don't need sync / ACK JGroups message.
(we didn't have one before and it worked ;-)
-Ales
On Apr 11, 2013, at 11:51 PM, Sanne Grinovero <sanne(a)hibernate.org> wrote:
There is a "blackhole" indexing backend, which pipes all
indexing
requests > /dev/null
Set this as an Infinispan Query configuration property:
default.worker.backend = blackhole
Of course that means that the index will not be updated: you might
need to adapt your test to tolerate that, but the point is not
functional testing but to verify how much the SYNC option on the
JGroups backend is actually slowing you down. I suspect the
performance penalty is not in the network but in the fact you're now
waiting for the index operations, while in async you where not waiting
for them to be flushed.
If you can identify which part is slow, then we can help you with
better configuration options.
On 11 April 2013 20:47, Ales Justin <ales.justin(a)gmail.com> wrote:
> What do you mean?
>
> On Apr 11, 2013, at 21:41, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>
> You could try the new sync version but setting the blackhole backend on the
> master node to remove the indexing overhead from the picture.
>
> On Apr 11, 2013 8:39 PM, "Sanne Grinovero" <sanne(a)hibernate.org>
wrote:
>>
>> 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.justin(a)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(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev