Adding a Load Profile

Use a load profile to consolidate all configurable aspects of the workload scoring system into a single named entity.

  1. In the left pane of the Administration Console, expand ASE Servers > Cluster Management, then select Load Profile.
  2. Click the drop-down arrow and select New.
  3. Select a cluster for the load profile.
  4. Enter a name for your profile.
  5. Specify the metric weights for the load profile.
    When a load profile is associated with a logical cluster, the workload manager calculates a load score for each instance in the logical cluster. This is calculated using the weight you entered for each metric, the raw value of each metric for the instance, and the workload measurement algorithm.
    The metrics measured by the server are:
    • User connections – the capacity of an instance to accept a new connection, based on resource availability.
    • CPU busy – the capacity of an instance to accept additional work.
    • Run-queue length – the number of runnable tasks on a system. The run-queue length measures the processing backlog, and is a good indicator of relative response time.
    • I/O load – outstanding asynchronous I/Os.
    • Engine deficit – the difference in the number of online engines among instances in the cluster. Engine deficit is measurable only when instances in the cluster have unequal numbers of engines. Engine deficit adds a metric for maximum relative capacity to the load score.
    • User-defined – an optional customer-supplied metric specific to the user’s environment.
  6. Enter values for:
    • Minimum Load Score – the load score is not a percentage, but is the minimum score the workload manager requires before it redirects work to other instances. The minimum load score is meaningful when compared to the load scores of other instances in the logical cluster using the load profile.
    • Login Redirection (%) – the load threshold for determining how best to distributed incoming connections.
    • Dynamic Connection Migration (%) – the load threshold that determines whether to distribute existing connections. The load threshold is the percentage difference between the load on the current instance and the load on the least-loaded instance currently participating in a logical cluster. That value must be met before the Cluster Edition redirects a login or migrates an existing connection.
    The percentages for Login Redirection and Dynamic Connection Migration are independent, and do not need to add up 100.
  7. (Optional) Click Summary to verify your selected options.