May 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-863) Eviction based on JVM memory utilization

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-863?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant closed ISPN-863. -------------------------------- Resolution: Duplicate Issue > Eviction based on JVM memory utilization > ---------------------------------------- > > Key: ISPN-863 > URL: https://issues.jboss.org/browse/ISPN-863 > Project: Infinispan > Issue Type: Enhancement > Components: Eviction > Affects Versions: 4.2.0.Final > Environment: N/A > Reporter: Dave Marion > Labels: eviction, threshold > > Allow user to specify percentage threshold upon which eviction will kick in and begin evicting entries based on the specified strategy. This would allow user to create a cache that will attempt to keep as many entries in memory as possible without having to specify maxEntries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5453) X-site state transfer: retry locally if local state push throws a SuspectException

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5453: ---------------------------------- Summary: X-site state transfer: retry locally if local state push throws a SuspectException Key: ISPN-5453 URL: https://issues.jboss.org/browse/ISPN-5453 Project: Infinispan Issue Type: Bug Components: Core, Cross-Site Replication Affects Versions: 7.2.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Fix For: 8.0.0.Alpha1 When the local state push command throws a {{SuspectException}}, we currently retry remotely unless the target node was already removed from the cache topology. This will fail with another {{SuspectException}}, so it would be better to retry locally the first time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5453) X-site state transfer: retry locally if local state push throws a SuspectException

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5453?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-5453: ---------------------------------- Assignee: (was: Dan Berindei) > X-site state transfer: retry locally if local state push throws a SuspectException > ---------------------------------------------------------------------------------- > > Key: ISPN-5453 > URL: https://issues.jboss.org/browse/ISPN-5453 > Project: Infinispan > Issue Type: Bug > Components: Core, Cross-Site Replication > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > When the local state push command throws a {{SuspectException}}, we currently retry remotely unless the target node was already removed from the cache topology. This will fail with another {{SuspectException}}, so it would be better to retry locally the first time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data

by Prashant Thakur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Prashant Thakur commented on ISPN-5452: --------------------------------------- We are presently using RMI service as both client and server are in Java at present > 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)

10 years, 11 months

1
0
0 / 0

[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: --------------------------------------- How do you use Hibernate Search with "remote RPC" ? What RPC technology is being tested? > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data

by Prashant Thakur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Prashant Thakur commented on ISPN-5452: --------------------------------------- Hi Adrain, I will try this fifth option as well. But performance of hibernate search is a killer for us for now. We are not getting this speed even with remote get calls of Infinispan i.e. 14k per thread per sec. Surely it seems we are missing something here. We will correct the RemoteQuery part definitely. Basically we are still working on DSL part of C++ , so for consistency within our applications we have kept it that way. Presently we are able to pass jpql from C++ Hot rod using a similar interface which is the first step towards moving to DSL. > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-5452: ------------------------------------- Hi Prashant, There is also a fifth method of running a query :), _org.infinispan.query.CacheQuery_. Have you tried/compared that with the other 4 options? Also, a short note on the usage of the RemoteQuery class. It should never be directly instantiated via its constructor even if that constructor appears to be public for now; a QueryBuilder should be used instead or you'll be exposing yourself to serious API breakage in 8.0. > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data

by Prashant Thakur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Prashant Thakur commented on ISPN-5452: --------------------------------------- Like to add that queries done without Index doesn't respond without index :) > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data

by Prashant Thakur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Prashant Thakur edited comment on ISPN-5452 at 5/10/15 1:17 AM: ---------------------------------------------------------------- Like to add that queries done without Index doesn't respond for long periods :) was (Author: prashant.thakur): Like to add that queries done without Index doesn't respond without index :) > 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)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5452) Query Execution using Hibernate Search slow for large volume data

by Prashant Thakur (JIRA)

[ https://issues.jboss.org/browse/ISPN-5452?page=com.atlassian.jira.plugin.... ] Prashant Thakur commented on ISPN-5452: --------------------------------------- 2) With HotRod we get 900 req/sec. 3) With Embedded mode its 3k req/ Per sec 4) With Hibernate search done with remote RPC we get approx 14k req/sec > 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)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2015