Package org.activiti.engine.impl.cfg
Class PerformanceSettings
java.lang.Object
org.activiti.engine.impl.cfg.PerformanceSettings
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected booleanExperimental setting: if true, whenever an execution is fetched from the data store, the whole execution tree is fetched in the same roundtrip.protected booleanExperimental setting: keeps a count on each execution that holds how many variables, jobs, tasks, event subscriptions, etc.protected booleanExperimental setting: in certain places in the engine (execution/process instance/historic process instance/ tasks/data objects) localization is supported.protected booleanIf false, no check will be done on boot. -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionbooleanbooleanbooleanbooleanvoidsetEnableEagerExecutionTreeFetching(boolean enableEagerExecutionTreeFetching) voidsetEnableExecutionRelationshipCounts(boolean enableExecutionRelationshipCounts) voidsetEnableLocalization(boolean enableLocalization) voidsetValidateExecutionRelationshipCountConfigOnBoot(boolean validateExecutionRelationshipCountConfigOnBoot)
-
Field Details
-
enableEagerExecutionTreeFetching
protected boolean enableEagerExecutionTreeFetchingExperimental setting: if true, whenever an execution is fetched from the data store, the whole execution tree is fetched in the same roundtrip. Less roundtrips to the database outweighs doing many, smaller fetches and often multiple executions from the same tree are needed anyway when executing process instances. -
enableExecutionRelationshipCounts
protected boolean enableExecutionRelationshipCountsExperimental setting: keeps a count on each execution that holds how many variables, jobs, tasks, event subscriptions, etc. the execution has. This makes the delete more performant as a query is not needed anymore to check if there is related data. However, maintaining the count does mean more updates to the execution and potentially more optimistic locking opportunities. Typically keeping the counts lead to better performance as deletes are a large part of the execution tree maintenance. -
validateExecutionRelationshipCountConfigOnBoot
protected boolean validateExecutionRelationshipCountConfigOnBootIf false, no check will be done on boot. -
enableLocalization
protected boolean enableLocalizationExperimental setting: in certain places in the engine (execution/process instance/historic process instance/ tasks/data objects) localization is supported. When this setting is false, localization is completely disabled, which gives a small performance gain.
-
-
Constructor Details
-
PerformanceSettings
public PerformanceSettings()
-
-
Method Details
-
isEnableEagerExecutionTreeFetching
public boolean isEnableEagerExecutionTreeFetching() -
setEnableEagerExecutionTreeFetching
public void setEnableEagerExecutionTreeFetching(boolean enableEagerExecutionTreeFetching) -
isEnableExecutionRelationshipCounts
public boolean isEnableExecutionRelationshipCounts() -
setEnableExecutionRelationshipCounts
public void setEnableExecutionRelationshipCounts(boolean enableExecutionRelationshipCounts) -
isValidateExecutionRelationshipCountConfigOnBoot
public boolean isValidateExecutionRelationshipCountConfigOnBoot() -
setValidateExecutionRelationshipCountConfigOnBoot
public void setValidateExecutionRelationshipCountConfigOnBoot(boolean validateExecutionRelationshipCountConfigOnBoot) -
isEnableLocalization
public boolean isEnableLocalization() -
setEnableLocalization
public void setEnableLocalization(boolean enableLocalization)
-