[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979038#comment-16979038 ] Lev Agafonov commented on IGNITE-11312: --- [~Pavlukhin], thank you for review. I take another time and found tests which is testing that JDBC thin client parameters showld work without 'ignite.jdbc' prefix [https://github.com/apache/ignite/blob/master/modules/clients/src/test/java/org/apache/ignite/jdbc/thin/JdbcThinConnectionSelfTest.java#L288] So, I need some more time to investigate the issue. > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Lev Agafonov >Priority: Major > Labels: newbie > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979001#comment-16979001 ] swy commented on IGNITE-12374: -- [~isapego] to make it simpler we have changed all fields to varchar to get rid of long-char conversion, together with the change of rebind instead of string copy. But the performance do not has too much difference but even worse(from 200 to 170TPS) because of the rebinding change. Attach is odbcsample.allchar.rebind.cc after change. Can you help to run the application in your environment to isolate environmental issue? > 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.allchar.rebind.cc, 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 > > 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;> > class="org.apache.ignite.configuration.IgniteConfiguration"> > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> > > > > > > class="org.apache.ignite.binary.BinaryBasicIdMapper"> > > > > > > > > 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)
[jira] [Updated] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] swy updated IGNITE-12374: - Attachment: odbcsample.allchar.rebind.cc > 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.allchar.rebind.cc, 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 > > 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;> > class="org.apache.ignite.configuration.IgniteConfiguration"> > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> > > > > > > class="org.apache.ignite.binary.BinaryBasicIdMapper"> > > > > > > > > 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)
[jira] [Commented] (IGNITE-12373) Handshake timeout while opening a channel connection from different nodes
[
https://issues.apache.org/jira/browse/IGNITE-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978519#comment-16978519
]
Amelchev Nikita commented on IGNITE-12373:
--
[~mmuzaf], Looks good to me.
> Handshake timeout while opening a channel connection from different nodes
> -
>
> Key: IGNITE-12373
> URL: https://issues.apache.org/jira/browse/IGNITE-12373
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Steps to reproduce,
> 1. Open transmission sender on the node1
> 2. Open transmission sender on the node2
> 3. Simultaneously send a file from node1 to node2 and from node2 to node1.
>
> {code:java}
> [2019-11-14
> 22:37:41,685][ERROR][async-runnable-runner-1][GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi]
> Failed to read from channel:
> java.nio.channels.AsynchronousCloseException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:407)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeTcpHandshake(TcpCommunicationSpi.java:3999)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioSession(TcpCommunicationSpi.java:3536)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.openChannel(TcpCommunicationSpi.java:4384)
> at
> org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi.openChannel(GridIoManagerFileTransmissionSelfTest.java:1068)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.openChannel(GridIoManager.java:1959)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$6500(GridIoManager.java:229)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.connect(GridIoManager.java:3145)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3244)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3194)
> at
> org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest.lambda$testFileHandlerCrossConnections$1(GridIoManagerFileTransmissionSelfTest.java:314)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$1(GridTestUtils.java:1039)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1095)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1416)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12373) Handshake timeout while opening a channel connection from different nodes
[
https://issues.apache.org/jira/browse/IGNITE-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978514#comment-16978514
]
Maxim Muzafarov commented on IGNITE-12373:
--
[~NSAmelchev]
I've fixed your comments. Can you take a look again?
> Handshake timeout while opening a channel connection from different nodes
> -
>
> Key: IGNITE-12373
> URL: https://issues.apache.org/jira/browse/IGNITE-12373
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Steps to reproduce,
> 1. Open transmission sender on the node1
> 2. Open transmission sender on the node2
> 3. Simultaneously send a file from node1 to node2 and from node2 to node1.
>
> {code:java}
> [2019-11-14
> 22:37:41,685][ERROR][async-runnable-runner-1][GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi]
> Failed to read from channel:
> java.nio.channels.AsynchronousCloseException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:407)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeTcpHandshake(TcpCommunicationSpi.java:3999)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioSession(TcpCommunicationSpi.java:3536)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.openChannel(TcpCommunicationSpi.java:4384)
> at
> org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi.openChannel(GridIoManagerFileTransmissionSelfTest.java:1068)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.openChannel(GridIoManager.java:1959)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$6500(GridIoManager.java:229)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.connect(GridIoManager.java:3145)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3244)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3194)
> at
> org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest.lambda$testFileHandlerCrossConnections$1(GridIoManagerFileTransmissionSelfTest.java:314)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$1(GridTestUtils.java:1039)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1095)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1416)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12373) Handshake timeout while opening a channel connection from different nodes
[
https://issues.apache.org/jira/browse/IGNITE-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978512#comment-16978512
]
Ignite TC Bot commented on IGNITE-12373:
{panel:title=Branch: [pull/7051/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4780037buildTypeId=IgniteTests24Java8_RunAll]
> Handshake timeout while opening a channel connection from different nodes
> -
>
> Key: IGNITE-12373
> URL: https://issues.apache.org/jira/browse/IGNITE-12373
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Steps to reproduce,
> 1. Open transmission sender on the node1
> 2. Open transmission sender on the node2
> 3. Simultaneously send a file from node1 to node2 and from node2 to node1.
>
> {code:java}
> [2019-11-14
> 22:37:41,685][ERROR][async-runnable-runner-1][GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi]
> Failed to read from channel:
> java.nio.channels.AsynchronousCloseException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:407)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeTcpHandshake(TcpCommunicationSpi.java:3999)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioSession(TcpCommunicationSpi.java:3536)
> at
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.openChannel(TcpCommunicationSpi.java:4384)
> at
> org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest$BlockingOpenChannelCommunicationSpi.openChannel(GridIoManagerFileTransmissionSelfTest.java:1068)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.openChannel(GridIoManager.java:1959)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$6500(GridIoManager.java:229)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.connect(GridIoManager.java:3145)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3244)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$TransmissionSender.send(GridIoManager.java:3194)
> at
> org.apache.ignite.internal.managers.communication.GridIoManagerFileTransmissionSelfTest.lambda$testFileHandlerCrossConnections$1(GridIoManagerFileTransmissionSelfTest.java:314)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$1(GridTestUtils.java:1039)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1095)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1416)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978443#comment-16978443 ] swy commented on IGNITE-12374: -- [~isapego] good catch, thanks. let me try again tomorrow 1. to rebind every time so that no string copy is needed 2. if column is LONG, will use SQLBindCol(p_hdl->stmt, value_no, *SQL_C_SLONG*, columns.buffer, ODBC_BUFFER_SIZE, ); is this what you mean? > 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 > > 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;> > class="org.apache.ignite.configuration.IgniteConfiguration"> > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> > > > > > > class="org.apache.ignite.binary.BinaryBasicIdMapper"> > > > > > > > > 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)
[jira] [Updated] (IGNITE-11987) [IEP-35] Add ability to configure metrics
[ https://issues.apache.org/jira/browse/IGNITE-11987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-11987: Labels: IEP-35 (was: IEP-35 await) > [IEP-35] Add ability to configure metrics > - > > Key: IGNITE-11987 > URL: https://issues.apache.org/jira/browse/IGNITE-11987 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Ignite should be able to: > * Configure Histogram metrics > * Configure HitRate metrics. > We should provide 2 ways to configure metric: > 1. -Configuration file.- Discussed on dev-list. Agreed to go with the > simplest solution - JMX method. > 2. JMX method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12353) Need to have additional sql benchmarks which covers Date types and inlining usage.
[ https://issues.apache.org/jira/browse/IGNITE-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978400#comment-16978400 ] Stanilovsky Evgeny commented on IGNITE-12353: - [~mmuzaf] thanks a lot, fix partially, plz take a look once more? > Need to have additional sql benchmarks which covers Date types and inlining > usage. > -- > > Key: IGNITE-12353 > URL: https://issues.apache.org/jira/browse/IGNITE-12353 > Project: Ignite > Issue Type: Improvement > Components: yardstick >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > Time Spent: 2.5h > Remaining Estimate: 0h > > In case of production operation with new versions occurs a need to check > additional sql request scenarios. Data fields with indexes and inline size - > one of it, additionally this test need to extend already existing > NativeSqlInsertDeleteBenchmark. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978395#comment-16978395 ] Igor Sapego commented on IGNITE-12374: -- [~yow] It looks like you are fetching LONG value as a SQL_CHAR and then cast it back to LONG. This can take really a lot of resources as we have not optimised casting code, so fetching values in not their real form can really affect performance. Please, try fetching value01 as SQL_C_SLONG > 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 > > 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;> > class="org.apache.ignite.configuration.IgniteConfiguration"> > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> > > > > > > class="org.apache.ignite.binary.BinaryBasicIdMapper"> > > > > > > > > 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)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978386#comment-16978386 ] Igor Sapego commented on IGNITE-12374: -- I think that binding will not take a lot of resources, so I think re-binding every time is OK. So, the main problem is in SELECT then. Let's take a closer look to this part. > 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 > > 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;> > class="org.apache.ignite.configuration.IgniteConfiguration"> > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> > > > > > > class="org.apache.ignite.binary.BinaryBasicIdMapper"> > > > > > > > > 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)
[jira] [Updated] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ 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 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;> 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 > > 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;> > class="org.apache.ignite.configuration.IgniteConfiguration"> > > class="org.apache.ignite.configuration.ClientConnectorConfiguration"/> > > > > > > class="org.apache.ignite.binary.BinaryBasicIdMapper"> > > > > > > > > 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)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978366#comment-16978366 ] swy commented on IGNITE-12374: -- fyi if we removed the SELECT query the application can reach 2500 TPS. > 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)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978358#comment-16978358 ] swy commented on IGNITE-12374: -- Thank you [~isapego], also I have doubt if we should rebind everytime a new value assigned to query, or instead reserve memory and copy the new value to the reserve. The later is what the application doing but is this a right thing to do? > 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)
[jira] [Commented] (IGNITE-12380) Add event for node validation failure.
[ https://issues.apache.org/jira/browse/IGNITE-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978329#comment-16978329 ] Amelchev Nikita commented on IGNITE-12380: -- [~PetrovMikhail], LGTM > Add event for node validation failure. > -- > > Key: IGNITE-12380 > URL: https://issues.apache.org/jira/browse/IGNITE-12380 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > Fix For: 2.8 > > Time Spent: 2h > Remaining Estimate: 0h > > It's needed record an event of a special type in case a node can't join the > topology due to a failure of its validation by existing nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978298#comment-16978298 ] Igor Sapego commented on IGNITE-12374: -- [~yow] I checked out the sample code and I have a feeling that performance drop may be related to atol and atof calls in sql_set_parameter. Need to check this though > 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)
[jira] [Commented] (IGNITE-12374) Too low performance ~200TPS for single ODBC client
[ https://issues.apache.org/jira/browse/IGNITE-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978296#comment-16978296 ] Igor Sapego commented on IGNITE-12374: -- [~yow] I just trying to locate where exactly the issue is, that's why I asked about native SQL. It's not like I propose you to use another API. I will investigate this and let you know. > 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)
[jira] [Commented] (IGNITE-12353) Need to have additional sql benchmarks which covers Date types and inlining usage.
[ https://issues.apache.org/jira/browse/IGNITE-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978259#comment-16978259 ] Stanilovsky Evgeny commented on IGNITE-12353: - may be someone else can merge it, otherwise it would be forgotten. > Need to have additional sql benchmarks which covers Date types and inlining > usage. > -- > > Key: IGNITE-12353 > URL: https://issues.apache.org/jira/browse/IGNITE-12353 > Project: Ignite > Issue Type: Improvement > Components: yardstick >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > In case of production operation with new versions occurs a need to check > additional sql request scenarios. Data fields with indexes and inline size - > one of it, additionally this test need to extend already existing > NativeSqlInsertDeleteBenchmark. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12380) Add event for node validation failure.
[ https://issues.apache.org/jira/browse/IGNITE-12380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PetrovMikhail updated IGNITE-12380: --- Description: It's needed record an event of a special type in case a node can't join the topology due to a failure of its validation by existing nodes. (was: It's needed to record an event of a special type in case a node can't join the topology due to a failure of its validation by existing nodes.) > Add event for node validation failure. > -- > > Key: IGNITE-12380 > URL: https://issues.apache.org/jira/browse/IGNITE-12380 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7.6 >Reporter: PetrovMikhail >Assignee: PetrovMikhail >Priority: Major > Fix For: 2.8 > > Time Spent: 2h > Remaining Estimate: 0h > > It's needed record an event of a special type in case a node can't join the > topology due to a failure of its validation by existing nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
