[
https://issues.apache.org/jira/browse/IGNITE-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683925#comment-15683925
]
Igor Sapego commented on IGNITE-4249:
-------------------------------------
Here is what I've found so far:
First I've profiled ODBC driver and here are results:
Socket Send took: 21 us
Socket Receive took: 44037 us
Entire SQLExecute call took: 44134 us
As you can see, almost 100% of the time driver spends waiting on the socket.
I assumed then that Java part (OdbcProcessor) execution takes a lot of time, so
I profiled Java part and here is result:
Java code execution takes: 2,965 us
Most of the time spent in getting query iterator.
So I've written simple test with Java SocketServer and C++ socket client which
send 1 byte to each other.
It takes 50 - 10000 us (most of the times <100 though)
So the only part I can think about now that takes all this time is Nio system.
> ODBC: Even simple request takes a lot of time.
> ----------------------------------------------
>
> Key: IGNITE-4249
> URL: https://issues.apache.org/jira/browse/IGNITE-4249
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Labels: odbc
> Fix For: 1.8
>
>
> Even if you submit very simple request with {{SQLExecute}} on a small data
> set, it's going to take ~40ms to be processed, while the same request in C++
> client takes ~200us.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
