[
https://issues.apache.org/jira/browse/IGNITE-16736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527817#comment-17527817
]
YuJue Li edited comment on IGNITE-16736 at 4/26/22 12:25 AM:
-------------------------------------------------------------
No special test code.
After creating the table, you only need to access the cluster through JMeter
and execute the INSERT statement.
INSERT statement is:
INSERT INTO tbl (a,b) VALUES (1,1), (2,2),
(3,3)................................;
During the test, the partitionAwareness parameter is true/false respectively.
was (Author: liyuj):
No special test code.
After creating the table, you only need to access the cluster through JMeter
and execute the INSERT statement.
INSERT statement is:
INSERT INTO tbl (a,b) VALUES (1,1), (2,2),
(3,3)................................;
During the test, the partitionAwareness parameter is true and false
respectively.
> Stress test JDBC Driver: partitionAwareness=true, the execution performance
> of INSERT statement becomes worse
> -------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-16736
> URL: https://issues.apache.org/jira/browse/IGNITE-16736
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 2.12
> Reporter: YuJue Li
> Priority: Major
> Attachments: partitionAwasome-false.png, partitionAwasome-true.png
>
>
> When use JDBC to perform the stress test of INSERT statement, you will find
> that the performance will deteriorate after partitionAwareness=true. In other
> scenarios, such as SQL query or KV read/write, the performance will be
> greatly improved, which is abnormal.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
