Guidelines for Improving Build Performance on Large Rule Projects

ILOG JRules User Guide > Creating Rule Projects > Concepts > Rule Project > Guidelines for Improving Build Performance on Large Rule Projects

Guidelines for Improving Build Performance on Large Rule Projects

PREVIOUS NEXT

To improve Rule Studio performance for large projects, you can use some Rule Studio build configurations which are better fitted to large projects.

Disable the Automatic Build

By default in Eclipse, a build process is launched as soon as a resource changes in the workspace. As a consequence, as soon as you save a file in Rule Studio, a build is launched. The build is usually incremental and fast, so there is no particular issue with the fact that it is launched regularly. But when you do modifications that have a global impact on the rule project, such as modifications on the business object model, the build may have to recheck a lot of elements, and become slow if your project is big.

You can toggle the Eclipse automatic build with the menu Project > Build Automatically.

Note

When the Eclipse automatic build is disabled, rule refactoring may not always be triggered, and you need to explicitly ask for a build to refresh the errors in the Problems view.

Set up Preferences for a Faster Build

When you have a large rule project, with many decision tables and ruleflows in particular, the build may become slower. Rule Studio lets you define preferences for the rule project build. You access the build preferences page by selecting Windows > Preferences, and then opening ILOG Rule Studio > Build.

When you save a rule project item, Rule Studio automatically generates IRL code and performs some checks on this code, including static rule analysis.

You can choose to disable the static rule analysis checks only, or to disable all checks by clearing the Perform IRL checks during build option. If you disable these options you will not receive warning and error messages when saving your rules, but the rule project build will be faster.

You can also disable the generation of IRL code to make the build even faster.

However if you disable these build options more time will be required when you extract a ruleset archive from the rule project, because the IRL code will be generated and checked at that point.