November 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8481) Lazily calculate hashCode for WrappedByteArray

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8481?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8481: ------------------------------------- Here is the JMH run from this https://gist.github.com/wburns/3744e3b2210466102378948cbb2105f0 It isn't much better if at all really compared to https://issues.jboss.org/browse/ISPN-8454?focusedCommentId=13485334&page=... but it should help when the entries are larger. The largest value here was only 1000 bytes > Lazily calculate hashCode for WrappedByteArray > ---------------------------------------------- > > Key: ISPN-8481 > URL: https://issues.jboss.org/browse/ISPN-8481 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > > We don't always use the hashCode for a WrappedByteArray. By always calculating it this adds additional cost, we should see if we can change this safely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8481) Lazily calculate hashCode for WrappedByteArray

by William Burns (JIRA)

William Burns created ISPN-8481: ----------------------------------- Summary: Lazily calculate hashCode for WrappedByteArray Key: ISPN-8481 URL: https://issues.jboss.org/browse/ISPN-8481 Project: Infinispan Issue Type: Sub-task Reporter: William Burns Assignee: William Burns We don't always use the hashCode for a WrappedByteArray. By always calculating it this adds additional cost, we should see if we can change this safely. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8454) Off Heap can crash when using JMH test

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8454?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8454: ------------------------------------- I was able to finally complete my JMH test run https://gist.github.com/wburns/d3fdc9bc707ba296374c31d99f6e7a05 > Off Heap can crash when using JMH test > -------------------------------------- > > Key: ISPN-8454 > URL: https://issues.jboss.org/browse/ISPN-8454 > Project: Infinispan > Issue Type: Bug > Components: Off Heap > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1 > > > I have a jmh branch from our benchmarks that always can crash off heap when not using tracing. For whatever reason I can't seem to reliably produce it with tracing. This JIRA is to handle this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8454) Off Heap can crash when using JMH test

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8454?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8454: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5562 > Off Heap can crash when using JMH test > -------------------------------------- > > Key: ISPN-8454 > URL: https://issues.jboss.org/browse/ISPN-8454 > Project: Infinispan > Issue Type: Bug > Components: Off Heap > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1 > > > I have a jmh branch from our benchmarks that always can crash off heap when not using tracing. For whatever reason I can't seem to reliably produce it with tracing. This JIRA is to handle this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8454) Off Heap can crash when using JMH test

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8454?page=com.atlassian.jira.plugin.... ] Work on ISPN-8454 started by William Burns. ------------------------------------------- > Off Heap can crash when using JMH test > -------------------------------------- > > Key: ISPN-8454 > URL: https://issues.jboss.org/browse/ISPN-8454 > Project: Infinispan > Issue Type: Bug > Components: Off Heap > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Beta1 > > > I have a jmh branch from our benchmarks that always can crash off heap when not using tracing. For whatever reason I can't seem to reliably produce it with tracing. This JIRA is to handle this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8403) Use partition handling for Shared Memory Service

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8403?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8403. -------------------------------- Resolution: Done > Use partition handling for Shared Memory Service > ------------------------------------------------ > > Key: ISPN-8403 > URL: https://issues.jboss.org/browse/ISPN-8403 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Core, State Transfer > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8405) Remove persistence from Shared Memory Service

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8405?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-8405. -------------------------------- Resolution: Done > Remove persistence from Shared Memory Service > --------------------------------------------- > > Key: ISPN-8405 > URL: https://issues.jboss.org/browse/ISPN-8405 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8406) Use number of owners provided by the user in Shared Memory Service

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8406?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8406: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jboss-container-images/jboss-dataservices-image/pull/21 > Use number of owners provided by the user in Shared Memory Service > ------------------------------------------------------------------ > > Key: ISPN-8406 > URL: https://issues.jboss.org/browse/ISPN-8406 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8467) Memory Leak in the Rest server

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8467?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8467: ------------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5561 > Memory Leak in the Rest server > ------------------------------ > > Key: ISPN-8467 > URL: https://issues.jboss.org/browse/ISPN-8467 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > The Netty rest server upon each connection will install the {{Http20RequestHandler}} that in turn creates a new instance of {{CacheOperations}} and {{RestCacheManager}} objects. > The {{RestCacheManager}} on every connection, among other things, will create hashmaps to keep cache instances, and will try to register every time a new {{RestSourceMigrator}} which gets accumulated in the {{RollingUpgradeManager}}. > Those objects should be shared across all channels so that they can efficiently cache resources and avoid creating lots of garbage. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6879) Calculate (and expose) minimum number of nodes for data in Infinispan

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6879?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-6879: ------------------------------------- True the more I thought about it max doesn't make that much sense. So a dynamic number based on current usage is what it should be. > Calculate (and expose) minimum number of nodes for data in Infinispan > --------------------------------------------------------------------- > > Key: ISPN-6879 > URL: https://issues.jboss.org/browse/ISPN-6879 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Server > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > With Kubernetes autoscaling we need to be able to tell what is the minimum amount of nodes necessary for hosting data (probably some sort of size + number of nodes estimation). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 2017