You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanislav Lukyanov (Jira)" <ji...@apache.org> on 2022/11/01 11:08:00 UTC
[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes
[ https://issues.apache.org/jira/browse/IGNITE-16760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stanislav Lukyanov updated IGNITE-16760:
----------------------------------------
Labels: fix-version-validated ignite-3 (was: ignite-3)
> Performance degradation of IgniteTables#tables after configuration changes
> --------------------------------------------------------------------------
>
> Key: IGNITE-16760
> URL: https://issues.apache.org/jira/browse/IGNITE-16760
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha4
> Reporter: Taras Ledkov
> Assignee: Denis Chudov
> Priority: Major
> Labels: fix-version-validated, ignite-3
> Fix For: 3.0.0-beta1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Performance degradation of configuration changes:
> Steps to reproduce:
> 1. Start cluster with 3 nodes
> 2. Run in the loop
> {code}
> CREATE TABLE TEST(ID INTEGER PRIMARY KEY, V INTEGER)
> for (Table t : ign.tables().tables()) {
> <DROP TABLE t.name()>;
> }
> {code}
> On begin {{IgniteTables#tables}} takes ~ 0.7 sec.
> The time of the operation is grown.
> The time after ~100 iteration is about 20 sec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)