Tidb: executor: distsql.selectResult is not necessary to fetch asynchronously.

Created on 29 Jul 2019  路  1Comment  路  Source: pingcap/tidb

Performance Questions

  • What version of TiDB are you using?

ebfb2ae on the master branch

  • What's the observed and your expected performance respectively?

distsql.selectResult uses kv.Response.Next() to fetch data from TiKV, since kv.Response is already asynchronously implemented by copIterator, perhaps distsql.selectResult is not necessary to fetch asynchronously again.

If deciding to do this, we need a benchmark result in avoiding performance regression.

good-first-issue siexecution statuhelp-wanted typenhancement typperformance typquestion

Most helpful comment

I am interested to investigate more on this issue, will start to read related source code!

>All comments

I am interested to investigate more on this issue, will start to read related source code!

Was this page helpful?
0 / 5 - 0 ratings