[JBoss JIRA] (ISPN-9849) Server should allocate less when looking up the cache
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9849?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9849:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 10.0.0.Beta2
Resolution: Done
> Server should allocate less when looking up the cache
> -----------------------------------------------------
>
> Key: ISPN-9849
> URL: https://issues.jboss.org/browse/ISPN-9849
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: performance
> Fix For: 10.0.0.Beta2
>
>
> * A composed String key is allocated to look up a decorated cache
> * Another composed String key is allocated to look up the {{CacheInfo}} object for that decorated cache. We could keep this map and remove the decorated caches map.
> * Reads decorate the cache with {{SKIP_STATISTICS}}, allocating a {{Flag[]}} and a {{DecoratedCache}} per request. I'd like to remove this wrapping, even if updating the statistics slows things down a bit, because without statistics there's no way to find the hit ratio of the cache.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-9849) Server should allocate less when looking up the cache
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9849?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9849:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6580
> Server should allocate less when looking up the cache
> -----------------------------------------------------
>
> Key: ISPN-9849
> URL: https://issues.jboss.org/browse/ISPN-9849
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: performance
>
> * A composed String key is allocated to look up a decorated cache
> * Another composed String key is allocated to look up the {{CacheInfo}} object for that decorated cache. We could keep this map and remove the decorated caches map.
> * Reads decorate the cache with {{SKIP_STATISTICS}}, allocating a {{Flag[]}} and a {{DecoratedCache}} per request. I'd like to remove this wrapping, even if updating the statistics slows things down a bit, because without statistics there's no way to find the hit ratio of the cache.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-10091) Add DNS_PING documentation
by Vittorio Rigamonti (Jira)
Vittorio Rigamonti created ISPN-10091:
-----------------------------------------
Summary: Add DNS_PING documentation
Key: ISPN-10091
URL: https://issues.jboss.org/browse/ISPN-10091
Project: Infinispan
Issue Type: Feature Request
Components: Documentation-Servers
Affects Versions: 9.4.11.Final, 10.0.0.Beta3
Reporter: Vittorio Rigamonti
Assignee: Vittorio Rigamonti
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-10090) Allow running TestNG tests without TestNGTestListener
by Dan Berindei (Jira)
Dan Berindei created ISPN-10090:
-----------------------------------
Summary: Allow running TestNG tests without TestNGTestListener
Key: ISPN-10090
URL: https://issues.jboss.org/browse/ISPN-10090
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core
Affects Versions: 9.4.11.Final, 10.0.0.Beta3
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 10.0.0.Beta4, 9.4.12.Final
{{AbstractInfinispanTest.testClassFinished}} fails when running from the IDE, because it checks for thread leaks but it doesn't properly ignore the JVM threads.
The workaround is to add listener {{org.infinispan.commons.test.TestNGTestListener}} to the default TestNG run configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-10089) Client Listeners should return the value on remove events
by Katia Aresti (Jira)
Katia Aresti created ISPN-10089:
-----------------------------------
Summary: Client Listeners should return the value on remove events
Key: ISPN-10089
URL: https://issues.jboss.org/browse/ISPN-10089
Project: Infinispan
Issue Type: Feature Request
Components: Listeners
Reporter: Katia Aresti
Client listeners return the key/value for added and updated values, but only return the key when we remove a value.
Remove notifications should include the value. If we only want to know which are the keys or the values that have been added, updated or removed, this can be configured directly on the annotation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months