[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978122#comment-16978122 ]
swy commented on IGNITE-12374: ------------------------------ Hi [~isapego] with native SQL interface the most can get is around 1000 TPS. But because of existing product limitatation the most we can scale is to 8 instances, and to backward compatible with existing API we have to use ODBC driver. So, if each instance only with 200 TPS the most performance we can have is only 200 X 8 = 1600 TPS. However, let's not bother our product limitation for now. May I know if anything wrong in the sample application? And is this result 200TPS(each transaction select+update) per instance is kind of expected result? Thanks. > Too low performance ~200TPS for single ODBC client > -------------------------------------------------- > > Key: IGNITE-12374 > URL: https://issues.apache.org/jira/browse/IGNITE-12374 > Project: Ignite > Issue Type: Improvement > Components: clients, odbc > Affects Versions: 2.7.5 > Environment: Ignite server run on top of Kubernetes, with 2 server > nodes, persistence enabled. Both CPU and RAM at server/client server is > sufficient according to system reports. > Reporter: swy > Priority: Major > Attachments: odbcsample.cc, values.yaml > > > Hi, in our test ignite performance with ODBC connection is too bad to proceed > with product integration. It is about ~200 TPS, each transaction with > select+update operation. > Please refer to attach sample program. It is just a simple test case. > Based on the profiling most of the time consumed by sql execution. Please > advice if the application did not do the right thing. > Thank you. > g++ -I/usr/include -I./ignite/binary/include -I./ignite/common/include > -I./ignite/common/os/linux/include -I./ignite/common/os/win/include > -I./ignite/core/include -I./ignite/jni/include odbcsample.cc -o odbcsample > -lodbc -L./ignite-libs/libignite.so -L./ignite-libs/libignite-odbc.so -- This message was sent by Atlassian Jira (v8.3.4#803005)