[JBoss JIRA] (ISPN-8004) Optimize serialization of encoders
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8004?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-8004:
---------------------------------------
Assignee: Gustavo Fernandes
> Optimize serialization of encoders
> ----------------------------------
>
> Key: ISPN-8004
> URL: https://issues.jboss.org/browse/ISPN-8004
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 9.1.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> Certain cache operations such streams, compute and functional commands require shipping the current associated encoder/wrapper to the cache instance to remote nodes.
> Currently, the Class<?> representing the encoder is sent over the wire, both for the key and for the value. It should be possible to associate an id to each encoder/wrapper and sent those instead
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ISPN-8004) Optimize serialization of encoders
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-8004?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-8004:
-----------------------------------
There are many situations where interning some data (class -> id, cache name -> id...) would be helpful. In Como [~NadirX] mentioned that implementing such replicated interning cache is troublesome in some way, e.g. when you expect that caches will startup & then merge. Not sure if the problems are limited to cache names interning.
> Optimize serialization of encoders
> ----------------------------------
>
> Key: ISPN-8004
> URL: https://issues.jboss.org/browse/ISPN-8004
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 9.1.0.CR1
> Reporter: Gustavo Fernandes
>
> Certain cache operations such streams, compute and functional commands require shipping the current associated encoder/wrapper to the cache instance to remote nodes.
> Currently, the Class<?> representing the encoder is sent over the wire, both for the key and for the value. It should be possible to associate an id to each encoder/wrapper and sent those instead
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ISPN-8082) Remove setSync from RocksDB WriteOptions
by Ryan Emerson (JIRA)
Ryan Emerson created ISPN-8082:
----------------------------------
Summary: Remove setSync from RocksDB WriteOptions
Key: ISPN-8082
URL: https://issues.jboss.org/browse/ISPN-8082
Project: Infinispan
Issue Type: Enhancement
Components: Loaders and Stores
Affects Versions: 9.1.0.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 9.1.1.Final
We should remove the setSync(true) option from the RocksDB writeOptions as this is not the default and severally impacts batch performance.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ISPN-5476) Cross-site tests should run in parallel
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5476?page=com.atlassian.jira.plugin.... ]
Dan Berindei reassigned ISPN-5476:
----------------------------------
Assignee: Dan Berindei
> Cross-site tests should run in parallel
> ---------------------------------------
>
> Key: ISPN-5476
> URL: https://issues.jboss.org/browse/ISPN-5476
> Project: Infinispan
> Issue Type: Task
> Components: Core, Cross-Site Replication, Test Suite - Core
> Affects Versions: 7.2.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.2.0.Final
>
>
> Currently the cross-site tests have to run in a single thread, and that means they're much slower than the regular core tests.
> It also means they need to run with a separate Maven profile, and that (combined with their duration) makes it very unlikely for devs to run the xsite tests on their machines.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months