November 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5934) ContinuousQuery must benefit from DSL based filter indexing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5934: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1283182|https://bugzilla.redhat.com/show_bug.cgi?id=1283182] from NEW to ASSIGNED > ContinuousQuery must benefit from DSL based filter indexing > ----------------------------------------------------------- > > Key: ISPN-5934 > URL: https://issues.jboss.org/browse/ISPN-5934 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta2, 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5934) ContinuousQuery must benefit from DSL based filter indexing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5934: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1283182 Bugzilla Update: Perform > ContinuousQuery must benefit from DSL based filter indexing > ----------------------------------------------------------- > > Key: ISPN-5934 > URL: https://issues.jboss.org/browse/ISPN-5934 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta2, 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5964) Drop the pre-JDK8 collections support

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5964?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5964: ---------------------------------- Status: Open (was: New) > Drop the pre-JDK8 collections support > ------------------------------------- > > Key: ISPN-5964 > URL: https://issues.jboss.org/browse/ISPN-5964 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 8.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5964) Drop the pre-JDK8 collections support

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5964?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5964: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3835 > Drop the pre-JDK8 collections support > ------------------------------------- > > Key: ISPN-5964 > URL: https://issues.jboss.org/browse/ISPN-5964 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Fix For: 8.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5963) Avoid allocating CompletableFuture instances for empty maps

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5963?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5963: ---------------------------------- Status: Open (was: New) > Avoid allocating CompletableFuture instances for empty maps > ----------------------------------------------------------- > > Key: ISPN-5963 > URL: https://issues.jboss.org/browse/ISPN-5963 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Trivial > Fix For: 8.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5963) Avoid allocating CompletableFuture instances for empty maps

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5963?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-5963: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3835 > Avoid allocating CompletableFuture instances for empty maps > ----------------------------------------------------------- > > Key: ISPN-5963 > URL: https://issues.jboss.org/browse/ISPN-5963 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Trivial > Fix For: 8.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5964) Drop the pre-JDK8 collections support

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-5964: ------------------------------------- Summary: Drop the pre-JDK8 collections support Key: ISPN-5964 URL: https://issues.jboss.org/browse/ISPN-5964 Project: Infinispan Issue Type: Task Components: Core Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 8.1.0.Beta2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5963) Avoid allocating CompletableFuture instances for empty maps

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-5963: ------------------------------------- Summary: Avoid allocating CompletableFuture instances for empty maps Key: ISPN-5963 URL: https://issues.jboss.org/browse/ISPN-5963 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 8.1.0.Beta2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5962) Implementation of RpcManagerImpl.invokeRemotely causes high CPU usage

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5962?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-5962: ----------------------------------- I found the comment here: http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u... > Implementation of RpcManagerImpl.invokeRemotely causes high CPU usage > --------------------------------------------------------------------- > > Key: ISPN-5962 > URL: https://issues.jboss.org/browse/ISPN-5962 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Beta1 > Reporter: Sanne Grinovero > > The method {{org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(Collection<Address>, ReplicableCommand, RpcOptions)}} is implemented by blocking on a {{CompletableFuture}}, but this then stalls on {{java.util.concurrent.CompletableFuture.waitingGet(boolean)}} by spending a significant amount of CPU time by spinning. > When implementing RPC calls and having to wait for remote operations, spinning is probably not a good idea. Could we try implementing this in some way to hint towards a more pessimistic lock? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5962) Implementation of RpcManagerImpl.invokeRemotely causes high CPU usage

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-5962?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-5962: --------------------------------------- That looks nice. But what does "acts much like a spin" mean exactly, will it still burn CPU time unnecessarily? We want this to lock pessimistically ASAP and free up the current thread.. actually encouraging context switching in this case. > Implementation of RpcManagerImpl.invokeRemotely causes high CPU usage > --------------------------------------------------------------------- > > Key: ISPN-5962 > URL: https://issues.jboss.org/browse/ISPN-5962 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.1.0.Beta1 > Reporter: Sanne Grinovero > > The method {{org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(Collection<Address>, ReplicableCommand, RpcOptions)}} is implemented by blocking on a {{CompletableFuture}}, but this then stalls on {{java.util.concurrent.CompletableFuture.waitingGet(boolean)}} by spending a significant amount of CPU time by spinning. > When implementing RPC calls and having to wait for remote operations, spinning is probably not a good idea. Could we try implementing this in some way to hint towards a more pessimistic lock? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015