[GitHub] [shardingsphere] xbkaishui commented on issue #6212: Optimize startup time， control which tables can load when startup

2020-09-03 Thread GitBox 


xbkaishui commented on issue #6212:
URL: https://github.com/apache/shardingsphere/issues/6212#issuecomment-686948660


   @tristaZero , Yes I am very appreciate for this task. 



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:
us...@infra.apache.org

[GitHub] [shardingsphere] xbkaishui commented on issue #6212: Optimize startup time， control which tables can load when startup

2020-07-02 Thread GitBox 


xbkaishui commented on issue #6212:
URL: https://github.com/apache/shardingsphere/issues/6212#issuecomment-652908481


   ok got it



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:
us...@infra.apache.org

[GitHub] [shardingsphere] xbkaishui commented on issue #6212: Optimize startup time， control which tables can load when startup

2020-07-01 Thread GitBox 


xbkaishui commented on issue #6212:
URL: https://github.com/apache/shardingsphere/issues/6212#issuecomment-652377840


   any update guys ? 



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:
us...@infra.apache.org

[GitHub] [shardingsphere] xbkaishui commented on issue #6212: Optimize startup time， control which tables can load when startup

2020-06-30 Thread GitBox 


xbkaishui commented on issue #6212:
URL: https://github.com/apache/shardingsphere/issues/6212#issuecomment-651592357


   for the single table metadata load, most of the latency time with be 1-4ms,  
for most case I think it is ok. 
   for the inconsistent metadata status,  it is acceptable 
   
   can we make the table load policy multi choose for user, not just load all 
tables, 
   this is also unacceptable in service mesh scene, which required elastic 
scale in and out. 



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:
us...@infra.apache.org

[GitHub] [shardingsphere] xbkaishui commented on issue #6212: Optimize startup time， control which tables can load when startup

2020-06-29 Thread GitBox 


xbkaishui commented on issue #6212:
URL: https://github.com/apache/shardingsphere/issues/6212#issuecomment-651141063


   I prefer the second solution,  lazy load 



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:
us...@infra.apache.org

[GitHub] [shardingsphere] xbkaishui commented on issue #6212: Optimize startup time， control which tables can load when startup

2020-06-29 Thread GitBox 


xbkaishui commented on issue #6212:
URL: https://github.com/apache/shardingsphere/issues/6212#issuecomment-651137167


   **I think we can solve this in two ways:** 
   1. for my case, one app load few tables,  can we just add a config to 
specify which tables want to load
   2. another way is can we use lazy load, I means loading table metadata we 
first used,  for the lazy load, this will be affect the performance for the 
first sql execution , this will be a trade off  
   



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:
us...@infra.apache.org