You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2023/10/11 09:37:00 UTC
[jira] [Updated] (IGNITE-20470) Ducktape to check dump performance
[ https://issues.apache.org/jira/browse/IGNITE-20470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikolay Izhikov updated IGNITE-20470:
-------------------------------------
Description:
Dump creation can affect transactions performance with change listener and disc operations. We must create ducktape test to check this.
Example test scenario:
* Start nodes
* Start transaction operations: insert, update, remove.
* Create dump
* Check dump consistency.
Measure
* Transaction performance penalty.
* GC utilization.
* Disc utilization.
Params:
* All types of caches(ATOMIC, TRANSACTIONAL) must be tested.
* In-memory caches are primary use-case, but persistence has to be tested, also.
was:
Dump creation can affect transactions performance with change listener and disc operations. We must create ducktape test to check this.
Example test scenario:
* Start nodes
* Start transaction operations: insert, update, remove.
* Create dump
* Check dump consistency.
Measure
* Transaction performance penalty.
* GC utilization.
* Disc utilization.
> Ducktape to check dump performance
> ----------------------------------
>
> Key: IGNITE-20470
> URL: https://issues.apache.org/jira/browse/IGNITE-20470
> Project: Ignite
> Issue Type: Task
> Reporter: Nikolay Izhikov
> Assignee: Sergey Korotkov
> Priority: Major
> Labels: IEP-109, ise
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Dump creation can affect transactions performance with change listener and disc operations. We must create ducktape test to check this.
> Example test scenario:
> * Start nodes
> * Start transaction operations: insert, update, remove.
> * Create dump
> * Check dump consistency.
> Measure
> * Transaction performance penalty.
> * GC utilization.
> * Disc utilization.
> Params:
> * All types of caches(ATOMIC, TRANSACTIONAL) must be tested.
> * In-memory caches are primary use-case, but persistence has to be tested, also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)