[
https://issues.apache.org/jira/browse/IGNITE-16760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-16760:
----------------------------------
Description:
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.
was:
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)
DROP TABLE TEST
{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.
> 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
> Priority: Major
> Labels: ignite-3
>
> 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)
