Re:Too slow to launch the service once ShardingJDBC is adopted

Hi Terry, Something came to my mind that the configuration item `max.connections.size.per.query`(Default value is 1) can impact the elapsed time of metadata loading, can you configure it higher? Juan Pan (Trista) Senior DBA & PPMC of Apache

Re:Too slow to launch the service once ShardingJDBC is adopted

Hi Terry, Thanks for your update. I want to make sure whether your sharding configuration contains the item, i.e., `defaultDataSourceName`? Our master branch has optimized the loading process of metaData for tables positioning in `defaultDataSource`. Based on that, if your team did not

Re:Too slow to launch the service once ShardingJDBC is adopted

Hi Terry, Actually, some improvements have been made [1]. If possible, could you compile the master branch to jar package and give it a test? Since I need to take some time to explore more about this issue from now on, I could only give you a rough time like three days or one week. Given Our

Re:Too slow to launch the service once ShardingJDBC is adopted

Hi Terry, Appreciated your detailed report. Currently, the option `check.table.metadata.enabled` is the best way to speed up launching. However much feedback from community made us consider to optimize it ASAP. Could i invite you to join us to make it better, even just an assisted test for