[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes

2022-11-01 Thread Stanislav Lukyanov (Jira) 


 [ 
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()) {
> ;
> }
> {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)

[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes

2022-06-30 Thread Taras Ledkov (Jira) 


 [ 
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()) {
;
}
{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()) {
> ;
> }
> {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)

[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes

2022-03-30 Thread Taras Ledkov (Jira) 


 [ 
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)
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.

  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 ~170 iteration is about 15 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)
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes

2022-03-30 Thread Taras Ledkov (Jira) 


 [ 
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)
DROP TABLE TEST
{code}

On begin {{IgniteTables#tables}} takes ~ 0.7 sec.
The time of the operation  is grown.
The time after ~170 iteration is about 15 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}

An iteration on the begin has about 0.7 sec. The time is grown.
The time after ~170 iteration is about 70 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)
> DROP TABLE TEST
> {code}
> On begin {{IgniteTables#tables}} takes ~ 0.7 sec.
> The time of the operation  is grown.
> The time after ~170 iteration is about 15 sec.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes

2022-03-30 Thread Taras Ledkov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-16760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Taras Ledkov updated IGNITE-16760:
--
Summary: Performance degradation of IgniteTables#tables after configuration 
changes  (was: Performance degradation of configuration changes)

> 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)
> DROP TABLE TEST
> {code}
> An iteration on the begin has about 1.7 sec. The time is grown.
> The time after ~170 iteration is about 70 sec.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (IGNITE-16760) Performance degradation of IgniteTables#tables after configuration changes

2022-03-30 Thread Taras Ledkov (Jira) 


 [ 
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)
DROP TABLE TEST
{code}

An iteration on the begin has about 0.7 sec. The time is grown.
The time after ~170 iteration is about 70 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}

An iteration on the begin has about 1.7 sec. The time is grown.
The time after ~170 iteration is about 70 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)
> DROP TABLE TEST
> {code}
> An iteration on the begin has about 0.7 sec. The time is grown.
> The time after ~170 iteration is about 70 sec.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)