Details
Description
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.
local ignite server, but the result same to remote container Ignite deployment too.
cat /etc/apache-ignite/my-config.xml
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <bean id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration"> <property name="clientConnectorConfiguration"> <bean class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> </property> <property name="binaryConfiguration"> <bean class="org.apache.ignite.configuration.BinaryConfiguration"> <property name="compactFooter" value="false"/> <property name="idMapper"> <bean class="org.apache.ignite.binary.BinaryBasicIdMapper"> <property name="lowerCase" value="true"/> </bean> </property> </bean> </property> </bean> </beans>
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