[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-5452:
---------------------------------------
Hi [~prashant.thakur],
your performance figures are not at all expected and extremely different than our testing results, and our QA teams do lots of different tests in many different scenarios and environments. When on a previous comment you mentioned RMI we where all extremely surprised :-)
So I would be interested in finding out more about your case, but you have to provide us with many more details to allow us to figure out what's wrong in your case. As I mentioned on the forum, you should profile your application and identify what the bottlenecks are. So unless you can provide more useful data we can't help.. I'd be glad to help though, so looking forward for any more details you might be able to provide.
We do have good experience with most freely available JVM profiling tools and also have licenses of some of the major commercial tools, so please use whatever tool you're more familiar with and share profiling session recordings, flight recorder logs, thread dumps or similar. Even just the output from a periodically running "vmstat" while youre benchmark is running would be helpful.
If I had to bet, your problem is in your application or in your benchmark; I'm not saying that to move the blame but simply a guess based on how far your results are from ours.. I sincerely hope it helps!
> 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)
9 years, 6 months
[JBoss JIRA] (ISPN-5522) LIRS BoundedConcurrentHashMapv8 eviction for tree bin missing check
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-5522?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-5522:
-------------------------------------
It is quite difficult to produce a test case for this. But it seems that essentially an entry in a TreeBin (that is a segment that had at least 8 elements in it) had an element that was at both the head of the LIRS hot stack and LIRS cold queue. It was being removed from both at the same time.
The first thread removed it from the LIRS hot stack making it to HIR_NONRESIDENT and setting the value to the NULL object and raising the notification
The second thread then removed from the cold queue and found it should transition to EVICTING since it was no longer in a queue. This then tried to raise the event since it didn't have the proper null check.
> LIRS BoundedConcurrentHashMapv8 eviction for tree bin missing check
> -------------------------------------------------------------------
>
> Key: ISPN-5522
> URL: https://issues.jboss.org/browse/ISPN-5522
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 7.2.2.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 8.0.0.Alpha2, 7.2.3.Final
>
>
> This was discovered at https://developer.jboss.org/message/932819?et=watches.email.thread
> The else if branch when a TreeBin is in place is missing a check to make sure eviction removal is only done if the value is non null.
> This line needs a {code} if (pv != null) {code} check around this [line|https://github.com/infinispan/infinispan/blob/40c2050c233c6fbfc382bd...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months
[JBoss JIRA] (ISPN-5521) Upgrade to Hibernate ORM 5.0.0.CR1
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-5521?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero updated ISPN-5521:
----------------------------------
Fix Version/s: 8.0.0.Alpha2
> Upgrade to Hibernate ORM 5.0.0.CR1
> ----------------------------------
>
> Key: ISPN-5521
> URL: https://issues.jboss.org/browse/ISPN-5521
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Loaders and Stores
> Reporter: Sanne Grinovero
> Assignee: Tristan Tarrant
> Fix For: 8.0.0.Alpha2
>
>
> I'm opening this to make sure we keep Infinispan aligned with the other platforms, now moving to Hibernate 5.
> This affects at least the JPA CacheStore, I'm not sure if other components.
> Among many improvements, noticeable for Infinispan there is better OSGi support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 6 months