[infinispan-issues] [JBoss JIRA] (ISPN-4847) Improve indexing performance

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015491#comment-13015491 ] 

Sanne Grinovero commented on ISPN-4847:
---------------------------------------

Right, I only mentioned HSEARCH-1681 so that if you have (write) benchmark tests which include the optimise(), keep in mind that some work isn't being done at index storage level.. so it might show an unfair result.

> Improve indexing performance
> ----------------------------
>
>                 Key: ISPN-4847
>                 URL: https://issues.jboss.org/browse/ISPN-4847
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Embedded Querying, Lucene Directory
>    Affects Versions: 7.0.0.CR1
>            Reporter: Radim Vansa
>            Assignee: Sanne Grinovero
>            Priority: Critical
>
> This JIRA is focused on optimizing performance of use case where the application uses short or none transactions - therefore, no batching can be applied - and then performs the query and expects that the result will be consistent (please, specify in documentation if any lag after cache.put() or tx.commit() is required and if the application can detect that the update has been applied).
> We are well aware (see BZ) that indexing can be implemented with very low overhead, but the throughput is thousands of times lower [1] (configuration in [2]) with distributed mode storing index in replicated cache, and about 4x slowdown when comparing replicated cache without indexing and indexing to NRT FS/RAM.
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-indexing/7/artifact/results/html/test_test.html
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-query-indexing/7/artifact/results/html/index.html



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)