[JBoss JIRA] (ISPN-7430) slowdown when using PutAll with transactions
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7430?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7430:
--------------------------------
Description:
when using puitAll for large batches with transactions , there is a significant slowdown in performance when compared to Infinispan 7.
skip_locking improves the speed
was:
when using puitAll for large batches with transactions , there is a significant slowdown in performance when compared to JDG 6.
skip_locking improves the speed
> slowdown when using PutAll with transactions
> --------------------------------------------
>
> Key: ISPN-7430
> URL: https://issues.jboss.org/browse/ISPN-7430
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha2
> Reporter: William Burns
> Assignee: William Burns
>
> when using puitAll for large batches with transactions , there is a significant slowdown in performance when compared to Infinispan 7.
> skip_locking improves the speed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 12 months
[JBoss JIRA] (ISPN-7430) slowdown when using PutAll with transactions
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7430?page=com.atlassian.jira.plugin.... ]
William Burns moved JDG-761 to ISPN-7430:
-----------------------------------------
Project: Infinispan (was: JBoss Data Grid)
Key: ISPN-7430 (was: JDG-761)
Workflow: GIT Pull Request with Triage workflow (was: CDW with loose statuses v1)
Component/s: Core
(was: unspecified)
Affects Version/s: 9.0.0.Alpha2
(was: JDG 7.0.0 GA)
> slowdown when using PutAll with transactions
> --------------------------------------------
>
> Key: ISPN-7430
> URL: https://issues.jboss.org/browse/ISPN-7430
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Alpha2
> Reporter: William Burns
> Assignee: William Burns
>
> when using puitAll for large batches with transactions , there is a significant slowdown in performance when compared to JDG 6.
> skip_locking improves the speed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 12 months
[JBoss JIRA] (ISPN-7428) PutAll does not scale (triangle)
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-7428?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-7428:
------------------------------
Description:
PutAll command for some reason now performs worse as the batch size grows. There must be some exponential computation done now that needs to be cleaned up.
The new algorithm used for the triangle splits the command per segments. This slows down everything:
From
Before: 2150 iterations (430 per thread)
After: 104 iterations (20.8 per thread)
-Note:-
* -The per-segments are only need for primary>backup communication. It is possible to split by primary owner in the originator and the primary owner would order and split by segment-
(already implemented...)
was:
PutAll command for some reason now performs worse as the batch size grows. There must be some exponential computation done now that needs to be cleaned up.
The new algorithm used for the triangle splits the command per segments. This slows down everything:
From
Before: 2150 iterations (430 per thread)
After: 104 iterations (20.8 per thread)
-Note:
* The per-segments are only need for primary->backup communication. It is possible to split by primary owner in the originator and the primary owner would order and split by segment.- (already implemented...)
> PutAll does not scale (triangle)
> --------------------------------
>
> Key: ISPN-7428
> URL: https://issues.jboss.org/browse/ISPN-7428
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: William Burns
> Assignee: Pedro Ruivo
>
> PutAll command for some reason now performs worse as the batch size grows. There must be some exponential computation done now that needs to be cleaned up.
> The new algorithm used for the triangle splits the command per segments. This slows down everything:
> From
> Before: 2150 iterations (430 per thread)
> After: 104 iterations (20.8 per thread)
> -Note:-
> * -The per-segments are only need for primary>backup communication. It is possible to split by primary owner in the originator and the primary owner would order and split by segment-
> (already implemented...)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 12 months
[JBoss JIRA] (ISPN-7428) PutAll does not scale (triangle)
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-7428?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-7428:
------------------------------
Description:
PutAll command for some reason now performs worse as the batch size grows. There must be some exponential computation done now that needs to be cleaned up.
The new algorithm used for the triangle splits the command per segments. This slows down everything:
From
Before: 2150 iterations (430 per thread)
After: 104 iterations (20.8 per thread)
-Note:
* The per-segments are only need for primary->backup communication. It is possible to split by primary owner in the originator and the primary owner would order and split by segment.- (already implemented...)
was:
PutAll command for some reason now performs worse as the batch size grows. There must be some exponential computation done now that needs to be cleaned up.
The new algorithm used for the triangle splits the command per segments. This slows down everything:
From
Before: 2150 iterations (430 per thread)
After: 104 iterations (20.8 per thread)
Note:
* The per-segments are only need for primary->backup communication. It is possible to split by primary owner in the originator and the primary owner would order and split by segment.
> PutAll does not scale (triangle)
> --------------------------------
>
> Key: ISPN-7428
> URL: https://issues.jboss.org/browse/ISPN-7428
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: William Burns
> Assignee: Pedro Ruivo
>
> PutAll command for some reason now performs worse as the batch size grows. There must be some exponential computation done now that needs to be cleaned up.
> The new algorithm used for the triangle splits the command per segments. This slows down everything:
> From
> Before: 2150 iterations (430 per thread)
> After: 104 iterations (20.8 per thread)
> -Note:
> * The per-segments are only need for primary->backup communication. It is possible to split by primary owner in the originator and the primary owner would order and split by segment.- (already implemented...)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 12 months