Upgrade/cel 0.12.0#28
Merged
Merged
Conversation
Add ability to compile CEL expressions once and execute them multiple times
with different contexts. This provides ~12x speedup over evaluate() when
reusing the same expression.
New API:
- compile(expression) -> Program
- Program.execute(context) -> result
Example:
program = compile('x + y')
program.execute({'x': 1, 'y': 2}) # 3
program.execute({'x': 10, 'y': 20}) # 30
Add examples demonstrating compile() and Program.execute() usage to README, quick-start guide, and Python API reference. Show performance pattern of compiling once and executing multiple times with different contexts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Key Changes
Behavior Notes
cel.evaluate("optional.of(42)") now returns cel.OptionalValue instead of a debug string.
Optional semantics preserved (optional.none() ≠ optional.of(null)).
compile()+execute() is ~6–8x faster for most expressions because it removes parse/compile from the hot path.
The list_size case barely improves because conversion dominates; the compile step is a smaller portion of the cost there.
Break‑even is very low (3–20 executions), so compile is worth it for any repeated evaluation.