himanshug commented on issue #8456: ingesting with high cardinality dimension have low performance URL: https://github.com/apache/incubator-druid/issues/8456#issuecomment-533239525 @quenlang I hope you figured things out by now, but just in case... it sounds like 1sec is the query time when things don't have to wait anywhere for resource as in the single threaded case. for the parallel case, I guess `12~14s` came from queries waiting in historical for processing thread pool (I would expect that be reported in `query/wait/time` metric at historical) . at historical , query is processed by processing each segment (needed for this query) in parallel using the processing thread pool which is of limited size (63 in your case) , when you sent parallel queries all cores were utilized. utilizing all the cores is actually a good thing :) things can be tuned based on the use cases , try to check the query metrics ( https://druid.apache.org/docs/latest/operations/metrics.html ) and take a look at https://druid.apache.org/docs/latest/operations/basic-cluster-tuning.html if you haven't .
---------------------------------------------------------------- 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 With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
