You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2018/08/02 20:44:19 UTC
[GitHub] egor-ryashin opened a new issue #6097: Possible performance issue
during DruidSchema metadata refresh
egor-ryashin opened a new issue #6097: Possible performance issue during DruidSchema metadata refresh
URL: https://github.com/apache/incubator-druid/issues/6097
`Druid Broker 0.11.0` with `druid.sql.enable=true` produces much more garbage than usual, profiling shows a lot of `Object[]` which are referenced by `TreeMap$Entry` which eventually leads to `io.druid.sql.calcite.schema.DruidSchema#refreshSegments`. I speculate it constantly refreshes metadata for every segment. With `-Xmx5G` and 1mln segments it leads to unresponsive service due to GC. Meanwhile it works fine with `druid.sql.enable=false`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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