You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/12/11 08:57:56 UTC

[GitHub] [shardingsphere] qwaszx92717 edited a comment on issue #8528: “in” query slow

qwaszx92717 edited a comment on issue #8528:
URL: https://github.com/apache/shardingsphere/issues/8528#issuecomment-742914942


   > Hi @qwaszx92717 ,
   > 
   > Thanks for your info.
   > ShardingSphere helps user handle SQLs queried in a database cluster though, the consuming time your provided is longer than expected.
   > The actual SQL is executed in MySQL using the index, isn't it?
   > Have you ever counted how many seconds one actual SQL takes? I am curious where that `15s` is used.
   
   This column have index.
   At that time,I connect some shading database and try to execute SQL in some sharding table. 
   example:select * from **table_1** where column in (...); this query speed is very fast(0.2s,the parameters are about 6000).
   after troubleshooting 
   Sharding log has no information when executing SQL.The above log will be printed until the execution is complete.
   excute record
   ![1607676359(1)](https://user-images.githubusercontent.com/24630042/101882701-33e85580-3bd1-11eb-9c5e-6ee8f65ff809.jpg)
   stack record
   ![image](https://user-images.githubusercontent.com/24630042/101882785-4cf10680-3bd1-11eb-9850-d1bb996b928c.png)
   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org