From issues-return-101989-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Dec 3 13:35:03 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id F0B6418065B for ; Tue, 3 Dec 2019 14:35:02 +0100 (CET) Received: (qmail 75423 invoked by uid 500); 3 Dec 2019 13:35:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 75409 invoked by uid 99); 3 Dec 2019 13:35:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2019 13:35:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 314A7E2E14 for ; Tue, 3 Dec 2019 13:35:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 49B9578024A for ; Tue, 3 Dec 2019 13:35:00 +0000 (UTC) Date: Tue, 3 Dec 2019 13:35:00 +0000 (UTC) From: "Stanilovsky Evgeny (Jira)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986896#comment-16986896 ] Stanilovsky Evgeny commented on IGNITE-12374: --------------------------------------------- after warmup, results are more better: [estanilovskiy@lab34 ~]$ ./run.sh 50 2000 =================================================== NumPartial: 50 NumCompleteRec: 2000 TolRec: 100000 Duration: 54 seconds TPS: 1852 =================================================== [estanilovskiy@lab34 ~]$ ./run.sh 50 2000 =================================================== NumPartial: 50 NumCompleteRec: 2000 TolRec: 100000 Duration: 48 seconds TPS: 2083 =================================================== [estanilovskiy@lab34 ~]$ ./run.sh 50 2000 =================================================== NumPartial: 50 NumCompleteRec: 2000 TolRec: 100000 Duration: 47 seconds TPS: 2128 =================================================== additionally i fix here : can you refactor code for multi-threaded client connection? > 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: ignite-9bb53f34.0.log, ignite-logs-config-source-20191128.zip, ignite-logs-config-source-20191129.zip, my-config-zstan.xml, odbcsample, odbcsample.allchar.rebind.cc, odbcsample.cc, profiling01.png, profiling03.png, profling02.png, screenshot-1.png, snapshot-1574845275597.nps, threaddump-1573207804944.tdump, threaddump-1574845414243.tdump, 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 > > 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"> > > > > > > > > > > > > > > > > > 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)