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 2020/05/27 03:27:34 UTC

[GitHub] [druid] richardstartin commented on issue #9920: Druid 0.13 ~ 0.18 version roaringbitmap benchmark becomes slow

richardstartin commented on issue #9920:
URL: https://github.com/apache/druid/issues/9920#issuecomment-633717928


   The code change in #6764 aimed to improve the performance of bitmap construction, and it applies run compression as the bitmap is built, but only to containers which are run-compressible. If this results in slower intersections in some cases, this can be fixed in the RoaringBitmap library; some changes were recently made to significantly improve run vs bitmap `andCardinality` and `intersects` and these changes are applicable to run vs bitmap `and`. 
   
   Note that #6764 will not have changed any behaviour when the roaring bitmaps have been memory mapped from disk and where run compression has already been applied (immediately before construction), which might explain if no regression has otherwise come to light since the change...


----------------------------------------------------------------
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



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