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 2019/06/29 08:12:37 UTC

[GitHub] [incubator-shardingsphere] fdlzp edited a comment on issue #2624: How should we add index after using sharding-jdbc?

fdlzp edited a comment on issue #2624: How should we add index after using sharding-jdbc?
URL: https://github.com/apache/incubator-shardingsphere/issues/2624#issuecomment-506937011
 
 
   the amount of data:20million
   query sql: above
   
   **Average Response Time**
   sharding: 2s      nosharding:20s
   
       after add index
      sharding: 700ms    nosharding:250ms
   
    **if it is possible :**
   
   Sharding-jdbc needs fixed time to parse/optimize..../merge SQL.
   But the amount of data is not large enough.
   The response time is too  short after add index.
   This cause we need more time to query after using sharding-jdbc.
   
   
   
   Or the use of index is not correct.
   
   
   Do you have any other ideas? or any suggestions?
   
   I'm increasing the amount of data.But it needs time.
   
   
   
   

----------------------------------------------------------------
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


With regards,
Apache Git Services