[
https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin....
]
Prashant Thakur commented on ISPN-5452:
---------------------------------------
HI Sanne,
One of the tests we did was using Hibernate Search independently where we got 50-100 us
kind of response. Can we do a similar tests in the setup above and confirm. This test is
missing in above result. The original question was Infinispan vs Hibernate Search.
The difference if its OK between these two we can do ahead and do profiling of our
application as well.
The above tests only confirm between Infinispan Embedded and Infinispan Remote. Not
Hibernate Search alone without infinispan.
WE did the same tests with the same hardware of these three scenarios. If you can confirm
from you end for 3rd scenario also that its still 300 us using hibernate search
independently then we are sure its an application issue.
Regards,
Prashant
Query Execution using Hibernate Search slow for large volume data
-----------------------------------------------------------------
Key: ISPN-5452
URL:
https://issues.jboss.org/browse/ISPN-5452
Project: Infinispan
Issue Type: Bug
Components: Configuration, Remote Querying
Affects Versions: 7.2.1.Final
Environment: Linux
Reporter: Prashant Thakur
While benchmarking Infinispan we found that Querying is very slow when compared with
Hibernate Search in Isolation
Single node of Infinispan
Memory allocated 230GB. No GC seen throughout query operation.
Total required after full GC was 122GB.
Setup 240 million records each of avg size 330 bytes .
System has 16 cores and 40 worker threads were allocated at server side.
With Single Client thread throughput was 900 req/sec in remote and 3k per sec in embedded
more same request with Hibernate Search in Isolation gives throughput of 14000 req/sec.
For 50 threads of clients the throughput was limited to 15k req/sec while hibernate
search gives 80k req/sec for 10 threads.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)