This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Table of Contents

Numerous distinct RuleSets and work classes affect performance


A developer asks: We are looking at setting up a Smart Dispute system with 400 clients and 400 RuleSets. Each client would have its own RuleSet. The list of RuleSets in the access group would be the only difference across the clients. With all the different RuleSets with the same rules be compiled differently? Will this affect the cache?

The Smart Dispute framework includes a sample class structure.

Suggested Approach

Yes, your approach would affect the cache, and some rules could get compiled differently. The fewer RuleSets you end up with in your approach, the better.

As a better approach, use a single client configuration RuleSet instead of the 400 RuleSets you're considering. The smaller number of RuleSets will ease future development and expansion of your system.

For the class group question: It is the class loader cache that gets affected in this case. Again, fewer is better - a smaller number of class groups will ease further system development.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.