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/06/29 08:57:23 UTC

[GitHub] [shardingsphere] hand515 commented on issue #6179: max.connections.size.per.query affects database performance

hand515 commented on issue #6179:
URL: https://github.com/apache/shardingsphere/issues/6179#issuecomment-651028620


   ```
   [INFO ColumnMetaDataLoader:84] - load column metadata for table=t1 use 192.2264ms
   [INFO IndexMetaDataLoader:62] - load index metadata for table=t1 use 38.0993ms
   [INFO ColumnMetaDataLoader:84] - load column metadata for table=t2 use 392.8141ms
   [INFO IndexMetaDataLoader:62] - load index metadata for table=t2 use 37.5664ms
   [INFO ColumnMetaDataLoader:84] - load column metadata for table=t3 use 267.1177ms
   [INFO IndexMetaDataLoader:62] - load index metadata for table=t3 use 38.5584ms
   [INFO ColumnMetaDataLoader:84] - load column metadata for table=t4 use 500.384ms
   [INFO IndexMetaDataLoader:62] - load index metadata for table=t4 use 38.3369ms
   ```
   
   Using 5.0-RC1 -SNAPSHOT, add some metric code in ColumnMetaDataLoader.load and IndexMetaDataLoader.load.
   
   The time is not related to the number of columns .
   
   Properties:
   ```
   max.connections.size.per.query: '10'
   sql.show: 'true'
   check.table.metadata.enabled: 'false'
   ```
   
   Client pings to db server: 29ms
   


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