[JBoss JIRA] (ISPN-10309) Convert Remaining Parts to Non Blocking & Reduce Thread Pools
by Will Burns (Jira)
Will Burns created ISPN-10309:
---------------------------------
Summary: Convert Remaining Parts to Non Blocking & Reduce Thread Pools
Key: ISPN-10309
URL: https://issues.jboss.org/browse/ISPN-10309
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Will Burns
Assignee: Will Burns
Fix For: 10.0.0.Final
We would love to get our thread pools down to a single CPU thread pool (size = numCores) and a blocking thread pool (arbitrarily large). We may also require a scheduler pool for various options as well (limited size 1-2?).
To do this we need to remove remnants of our blocking code as possible. Possible issues for blocking are mostly around locks and io operations.
The persistence layer was completed with ISPN-9722 so that is not an issue.
The requirement around locking can be relaxed if the locks are guaranteed to be small in scope and do not wrap other blocking operations. An example would be a lock such as ones in CHM as long as we don't have large blocks for functional argument types.
If code cannot be made non blocking we must offload the operation to the blocking thread pool. Care must be taken to ensure that once the blocking portion of code is completed that we switch back the to CPU thread pool as soon as possible. The listener API for example is violating this and will run code in Infinispan from any thread that completes the listener that could be done from a user.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ISPN-10307) Jackson Databind 2.9.8
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-10307:
--------------------------------------
Summary: Jackson Databind 2.9.8
Key: ISPN-10307
URL: https://issues.jboss.org/browse/ISPN-10307
Project: Infinispan
Issue Type: Component Upgrade
Components: Build
Affects Versions: 9.4.14.Final, 10.0.0.Beta3
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.0.0.Beta4, 9.4.15.Final
This fixes multiple CVEs.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ISPN-10290) JGroupsTransport.invokeCommandStaggered allocates too much
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10290?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-10290:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> JGroupsTransport.invokeCommandStaggered allocates too much
> ----------------------------------------------------------
>
> Key: ISPN-10290
> URL: https://issues.jboss.org/browse/ISPN-10290
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.Beta3, 9.4.14.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Fix For: 10.0.0.Beta4
>
>
> I assumed the {{logRequest(requestId, command, "staggered " + targets)}} call would be inlined and the JIT would eliminate the allocation when trace logging is disabled, but apparently that doesn't always happen, and a {{StringBuilder}} instance is always created.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months