Implement query graph pruning #67
Labels
level:medium
This issue is of average difficulty
priority:high
Priority: high
type:feature
New feature
zone:performance
Making the database faster
Milestone
Ignore query graph paths that are "too branched".
Intuitively, When we have something like
{AA BB CC DD ?? ?? ?? ?? ?? ?? EE FF GG HH}
we should just split this into{AA BB CC DD} & {EE FF GG HH}
.Implementation-wise, compute
branching level
(using ngram density estimation) for every node, and collapse nodes where it's too big.This is a blocking issue for releasing query graphs, because without it some queries will not be stable enough.
The text was updated successfully, but these errors were encountered: