Avoid parsing DMN decisions for every evaluation #8571
Labels
area/performance
Marks an issue as performance related
backport stable/8.2
Backport a pull request to 8.2.x
component/engine
impact/high
Marks issues relieving a recurring pain or fulfilling an immediate need
kind/toil
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
scope/broker
Marks an issue or PR to appear in the broker section of the changelog
support
Marks an issue as related to a customer support request
version:8.1.16
Marks an issue as being completely or in parts released in 8.1.16
version:8.2.12
Marks an issue as being completely or in parts released in 8.2.12
version:8.3.0-alpha5
Marks an issue as being completely or in parts released in 8.3.0-alpha5
version:8.3.0-alpha6
Marks an issue as being completely or in parts released in 8.3.0-alpha6
version:8.3.0
Marks an issue as being completely or in parts released in 8.3.0
Milestone
Description
The DMN engine parses a DMN resource into an in-memory data object that is used to evaluate the decision. The parsing of DMN decisions is (relatively) costly. Instead of parsing it every time, we can cache the parsed DMN (e.g. using an LRU cache).
Relates to https://jira.camunda.com/browse/SUPPORT-17656
The text was updated successfully, but these errors were encountered: