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

swy updated IGNITE-12374:
-------------------------
    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

  was:
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


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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to