Versions Compared

Old Version 15

changes.mady.by.user Felicity Borrelli

Saved on

compared with

New Version 16

changes.mady.by.user Felicity Borrelli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Private_Edition_flag.png

Excerpt
namePartition Profile explanation (4.3)

The Partition profile has been created as part of the batch scaling solution. In the profile configuration, you define the max Scale Factor and the field from the UDRs that will be the Key for the partitioned data.

Configuration

To create a new Scalable Partition profile configuration, click New Configuration and select Partition Profile from the Configurations dialog.

The profile configuration contains two tabs; General and Association.

General tab

The General tab is displayed by default when creating or opening the Partition Profile. This is where you define the Max Scale Factor, ; the maximum number of partitions to be created within your batch scaling solution.

prtition_profile_general_tab.png
Tip

Hint!

When setting the Max Scale Factor, you are defining the number of partitions, which determines the level of parallelism you can achieve. While you should choose a number large enough to handle expected workloads, avoid going too big, as excessively high numbers can strain system resources or lead to inefficiencies if the data isn’t evenly distributed. A good approach is to select a Max Scale Factor that is divisible by many numbers, as this allows for a more balanced distribution of workloads across workflows. For example, numbers like 6, 12, or 30 work well because they can be evenly divided by a wide range of values.

Association Tab

In the Association tab, you can configure rules that are used to match an incoming UDR with a session. Every UDR type requires a set of rules that are processed in a certain order. In most cases, only one rule per incoming UDR type is defined.

You can use a primary expression to filter out UDRs that are candidates for a specific rule. If the UDR is filtered out by the primary expression, it is matched with the existing sessions by using one or several ID fields as a key.

For UDRs with ID Fields matching an existing session, an additional expression may be used to specify additional matching criteria. For example, if dynamic IP addresses are provided to customers based on time intervals, the field that contains the IP address could be used in ID Fields while the actual time could be compared in Additional Expression.

partition_profile_association_tab.png

...