July 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5630) Port tests from enty retriever

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5630?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5630: -------------------------------- Status: Open (was: New) > Port tests from enty retriever > ------------------------------ > > Key: ISPN-5630 > URL: https://issues.jboss.org/browse/ISPN-5630 > Project: Infinispan > Issue Type: Sub-task > Components: Test Suite - Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Beta2 > > > This is to port the various entry retriever tests to get similar coverage for distributed streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5630) Port tests from enty retriever

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5630?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5630: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3602 > Port tests from enty retriever > ------------------------------ > > Key: ISPN-5630 > URL: https://issues.jboss.org/browse/ISPN-5630 > Project: Infinispan > Issue Type: Sub-task > Components: Test Suite - Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Beta2 > > > This is to port the various entry retriever tests to get similar coverage for distributed streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5630) Port tests from enty retriever

by William Burns (JIRA)

William Burns created ISPN-5630: ----------------------------------- Summary: Port tests from enty retriever Key: ISPN-5630 URL: https://issues.jboss.org/browse/ISPN-5630 Project: Infinispan Issue Type: Sub-task Components: Test Suite - Core Reporter: William Burns Assignee: William Burns Fix For: 8.0.0.Beta2 This is to port the various entry retriever tests to get similar coverage for distributed streams. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5416) Grouping and aggregations with DSL based queries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5416?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5416: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.0.0.Beta2 Resolution: Done > Grouping and aggregations with DSL based queries > ------------------------------------------------ > > Key: ISPN-5416 > URL: https://issues.jboss.org/browse/ISPN-5416 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > Implement the 'group by' statement and the aggregate functions: count, sum, average, min, max. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 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 Sanne, We have been doing some profiling and changes to improve around BuildSearcher piece. We observed that if codec is changed to org.apache.lucene.codecs.bloom for fields which are discrete there is huge dip in buildSearcher part. Can you please look at providing this as configuration with other annotations. We also see that most part of time is spent in Parsing If we have something like bind variables in Oracle and reuse the query plan with change in just parameter it would save alot of time and we can expect 2x improvement than current speed. I saw a ticket being raised for same https://issues.jboss.org/browse/ISPN-5414 . If there is some work already in progress and you would wish us to contribute in testing or coding please let us know . This is an absolute must for achieving the performance figures and we would like to avoid duplication of effort. Regarding 2nd question Test run have the same number of Keys and Same number of queries. So we are sure multiple queries are not fired. For sample data I am attaching the profiling info in attached excel sheet where we see time spent in various phases. Please let us know if you require extra information > 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, 8.0.0.Final > Environment: Linux > Reporter: Prashant Thakur > Attachments: Infinispan Dist Cache.xlsx, profiling_results.7z > > > 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, 5 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 updated ISPN-5452: ---------------------------------- Attachment: Infinispan Dist Cache.xlsx Comparision of Infinispan and Hibernate flows > 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, 8.0.0.Final > Environment: Linux > Reporter: Prashant Thakur > Attachments: Infinispan Dist Cache.xlsx, profiling_results.7z > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5612) Make filter by segment more efficient in the Remote iterator

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5612?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-5612. --------------------------------- Fix Version/s: 8.0.0.Beta2 8.0.0.Final (was: 8.0.0.CR1) Resolution: Done > Make filter by segment more efficient in the Remote iterator > ------------------------------------------------------------ > > Key: ISPN-5612 > URL: https://issues.jboss.org/browse/ISPN-5612 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 8.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > The {{org.infinispan.server.hotrod.iteration.IterationManager}} is based on the EntryRetriever, and segment filtering is currently done via a custom {{KeyValueFilterConverter}}, that needs to be run on all nodes. > In the case where all segments to be filtered on are owned by the server holding the iteration, it should skip iterating on the remote nodes altogether. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-694) Create expiration notification for in-memory cache entries

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-694?page=com.atlassian.jira.plugin.s... ] Work on ISPN-694 started by William Burns. ------------------------------------------ > Create expiration notification for in-memory cache entries > ---------------------------------------------------------- > > Key: ISPN-694 > URL: https://issues.jboss.org/browse/ISPN-694 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Environment: any > Reporter: Edouard Boily > Assignee: William Burns > Fix For: 8.0.0.Final > > Attachments: 01.patch > > > Create a CacheEntryExpired notification and make EvictionManager send this notification when a cache entry is evicted because it is expired. > Also mage sure the cache entry value is sent over in the event. > CacheEntryEvicted notification should also send the entry value in the event. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5620) Create PendingLockManager

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5620?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5620: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create PendingLockManager > ------------------------- > > Key: ISPN-5620 > URL: https://issues.jboss.org/browse/ISPN-5620 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 8.0.0.Beta2 > > > PendingLockManager will be responsible to check for older topology id transaction that may have locks acquired. Newer transactions would have to wait for them to complete before proceeding in lock acquisition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5629) AvgAccumulator should handle NaN and other non-numbers

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5629: ----------------------------------- Summary: AvgAccumulator should handle NaN and other non-numbers Key: ISPN-5629 URL: https://issues.jboss.org/browse/ISPN-5629 Project: Infinispan Issue Type: Bug Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.0.0.Final The handling should be similar to java.util.DoubleSummaryStatistics -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2015