[GitHub] [incubator-druid] himanshug commented on issue #8125: Leave a single CachePopulator and choose sync/async mode automatically

[GitBox <gi...@apache.org>]

himanshug commented on issue #8125: Leave a single CachePopulator and choose sync/async mode automatically
URL: https://github.com/apache/incubator-druid/issues/8125#issuecomment-514837508
 
 
   > is it really a good idea to try to compute cache entries asynchronously and in parallel?
   
   I think, no . it is ok to compute the entry in the same thread reading sequence.
   
   > is it a good idea to have background cache population be a generic thing at all? What if we only had foreground population and left it up to the individual Cache impls to do background pushing to remote cache servers if they want to?
   
   it makes sense to leave that choice to cache impl instead of user, but all remote caches would need to do it in the background and would end up writing same type of code. it will be useful for that common code to be made available in druid core so that remote cache extensions could just use 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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org