[ https://issues.apache.org/jira/browse/IGNITE-16760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626580#comment-17626580 ]
Stanislav Lukyanov commented on IGNITE-16760: --------------------------------------------- The change was committed with an incorrect Jira ID (IGNITE-16670): [https://github.com/apache/ignite-3/commit/bb268f4c00b240edfa637d8b0a6e397d17472fc6] Nothing we can do about this now. > 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: 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)