Jira (PDB-5260) Improve PQL parse performance with high number of filter clauses

[David McTavish (Jira)]

David McTavish updated an issue

PuppetDB / PDB-5260 Improve PQL parse performance with high number of filter clauses Change By: David McTavish Summary: Fix Improve PQL parse performance problems with high number of filter clauses Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)

[Rob Browning (Jira)]

Rob Browning assigned an issue to Rob Browning

PuppetDB / PDB-5260 Improve PQL parse performance with high number of filter clauses

Change By: Rob Browning Assignee: Rob Browning

Add Comment

[Rob Browning (Jira)]

Rob Browning updated an issue

PuppetDB / PDB-5260 Improve PQL parse performance with high number of filter clauses

Change By: Rob Browning Fix Version/s: PDB 7.10.1 Fix Version/s: PDB 6.20.3 Release Notes: Bug Fix Release Notes Summary: PuppetDB should require much less time and memory when parsing some PQL queries, , for example queries including many or clauses like `nodes {x or y or ...}`.  Previously 5000 clauses could not be parsed with an 8GB heap, and much smaller queries still required exorbitant amounts of memory and CPU time.

Add Comment

[Rob Browning (Jira)]

Rob Browning commented on PDB-5260

Re: Improve PQL parse performance with high number of filter clauses Just to record this here, another case that if relevant might nudge us toward fixing it more comprehensively is any situations where we accept user pql or user pql fragments (from some ui) that we combine into a broader query.

Add Comment

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)

[Rob Browning (Jira)]

Rob Browning commented on PDB-5260

Re: Improve PQL parse performance with high number of filter clauses

Oh, and also we did address the earlier, immediate problem by rewriting some of the production rules – was sufficient for at least that case.

Add Comment