In server.yaml, followling props effect the concurrency, you can have a try.

max.connections.size.per.query: 64
acceptor.size: 64
executor.size: 64

--

Zhang Yonglun
Apache ShardingSphere


Kai Yu <freeza1...@outlook.com> 于2020年6月3日周三 下午3:16写道:

> Hi ALL :
>     we have a project used 16 databases (db0 ...db15),we used
> sharding-proxy 4.0.0-RC2 ,
> and config the sharding.xml like this:
> schemaName: ty-basic-member
> dataSources:
>   db0:
>     url: jdbc:mysql://xxx:3306/db0?useSSL=false
>     username: root
>     password: root
>     connectionTimeoutMilliseconds: 30000
>     idleTimeoutMilliseconds: 60000
>     maxLifetimeMilliseconds: 1800000
>     maxPoolSize: 65
> ...
>   db15:
>     url: jdbc:mysql://xxx:3306/db15?useSSL=false
>     username: root
>     password: root
>     connectionTimeoutMilliseconds: 30000
>     idleTimeoutMilliseconds: 60000
>     maxLifetimeMilliseconds: 1800000
>     maxPoolSize: 65
>
> shardingRule:
>   tables:
>     member:
>       actualDataNodes:
> dwj|13.member,dwj|12.member,dwj|11.member,dwj|10.member,dwj|5.member,dwj|6.member,dwj|7.member,dwj|15.member,dwj|8.member,dwj|14.member,dwj|9.member,dwj|0.member,dwj|0.member,dwj|1.member,dwj|2.member,dwj|3.member,dwj|4.member
>       databaseStrategy:
>         complex:
>           algorithmClassName:
> com.toonyoo.app.sharding.proxy.ProxyDBShardingAlgorithm
>           shardingColumns: merchant_id,member_id
>       logicTable: member
>
> there is a table named member, it has 3kw rows,  then we test the query
> like this :
> case 1
>     we connect to the sharding-proxy application (like ip:3307 ) on server
> , execute count sql:
> MySQL [ty-basic-member]> select count(*) from member where merchant_id =
> 'dwj';
> +----------+
> | count(*) |
> +----------+
> | 34202355 |
> +----------+
> 1 row in set (37.59 sec)
>
> case 2
>    we connect to  db0 on server , executecount sql:
>   MySQL [db0]> select count(*) from member where merchant_id = 'dwj';
> +----------+
> | count(*) |
> +----------+
> | 2217826 |
> +----------+
> 1 row in set (5.49 sec)
>
>
> we found the  count query cost 37s with 16 database ,
> we think the proxy component deal the 16database's query  may cost 5s like
> count query on db0 ,looks like Parallel ,we dont know why.
>
> Can you provide some technical details underlying principle for us to
> understand?
> thanks
>

Reply via email to