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.
I'm sorry I didn't make it clear. I'll give you another description
The problem I have encountered is that when there are too many query
conditions, the query speed will be very slow. When 'in' params are 5000 or
more , the query time will be about 10 seconds.
(select * from table where FILEINDEXID in('1021725517717865',......)
This colunm have index.
KEY `FILEID` (`FILEID`) USING BTREE
excute record
When I execute the SQL directly in one of the sharding tables of a sharding
database, the query speed is faster (about 0.2S)
(select * from table_1 where FILEINDEXID in('1021725517717865',......)
after troubleshooting
Sharding log has no information when executing SQL.When the execution is
completed, the following log will be printed.
When printing stack information, the stack information for executing SQL is
as follows
----------------------------------------------------------------
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:
[email protected]
