nozjkoitop opened a new pull request, #19004:
URL: https://github.com/apache/druid/pull/19004

   ### Description
   
   In some of our environments we observed a significant query performance 
regression after upgrading to Druid 29.0. This regression appears to be related 
to the virtual column bitmap indexing optimization introduced in 
https://github.com/apache/druid/pull/15585 and 
https://github.com/apache/druid/pull/15633.
   
   While the change improves performance for many cases by enabling bitmap 
index creation for expression-based virtual columns, we found that in certain 
workloads the index computation becomes unexpectedly expensive. In our 
deployments, building these indices accounted for more than 90% of the CPU 
usage on Historical nodes during query execution, leading to severe degradation 
in overall query latency.
   
   For one representative workload, the average query runtime increased from 
10.01 seconds to 150.18 seconds compared to earlier versions. Once 
expression-based virtual column bitmap index creation was disabled, the 
regression disappeared and query performance returned to expected levels.
   
   This PR addresses this issue by preventing the optimization from triggering 
in scenarios where the cost of index computation outweighs its benefit, 
avoiding major regressions in affected environments.
   
   Added a new query context parameter, `maxVirtualColumnsForBitmapIndexing` 
(default: `Integer.MAX_VALUE`), which sets the virtual-column count threshold 
beyond which Druid stops using bitmap indexes for filters on virtual columns.
   
   #### Release note
   
   Adds a safeguard to skip virtual-column bitmap indexing when it is likely to 
be counterproductive, falling back to non-indexed filtering to preserve 
expected performance. 
   
   <hr>
   
   <!-- Check the items by putting "x" in the brackets for the done things. Not 
all of these items apply to every PR. Remove the items which are not done or 
not relevant to the PR. None of the items from the checklist below are strictly 
necessary, but it would be very helpful if you at least self-review the PR. -->
   
   This PR has:
   
   - [x] been self-reviewed.
   - [x] added documentation for new or modified features or behaviors.
   - [x] a release note entry in the PR description.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md)
   - [ ] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [x] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] added integration tests.
   - [x] been tested in a test Druid cluster.


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to