You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2025/01/16 11:16:00 UTC
[jira] [Assigned] (IGNITE-24221) Prepare/Adjust benchmarks in order to measure puts and gets and zones/tables creation within collocation track
[ https://issues.apache.org/jira/browse/IGNITE-24221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin reassigned IGNITE-24221:
--------------------------------------------
Assignee: Vyacheslav Koptilin
> Prepare/Adjust benchmarks in order to measure puts and gets and zones/tables creation within collocation track
> ---------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-24221
> URL: https://issues.apache.org/jira/browse/IGNITE-24221
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> In order not to miss the performance problems during collocation epic implementation it would be nice to have and run several benchmarks from the very beginning. Seems that at least the following benchmarks will be helpful:
> # Zone/Table creation benchmarks.
> # Adjusted versions of InsertBenchmark and SelectBenchmark in order to check whether multiple tables in one replica are as fast as dedicated tables.
> ## Given adjusted benchmarks will be removed when we will switch may to collocation rails.
> ## In order to enable collocation logic it's required to set feature flag `IGNITE_ZONE_BASED_REPLICATION`.
> ## Besides that, it's required to mock `PlacementDriver` in a way that it will return the proper primary replica that hosts zone one.
> h3. Definition of Done
> * Zone/Table creation benchmarks are implemented.
> * Adjusted versions of InsertBenchmark and SelectBenchmark are implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)