Allocating blocks of Next-IDs for faster create operations
To increase performance during a create operation, you can configure the BMC Remedy AR System server to allocate Next-IDs in blocks rather than one at a time.
This setting is always disabled on the Distributed Pending form so that BMC Remedy Distributed Server Option (DSO) can operate correctly.
To allocate Next-ID blocks
Set the Next-ID-Block-Size value to a positive number up to 1000 in the AR System Configuration Generic UI form, for example:
The default value is 1. If 0 or a negative number (for example, -1) is used, the server will use the default value. You do not need to restart the server for the change to take effect. For more information, see Configuration-settings-N-R.
To disable this option, set the value of Next-ID-Block-Size to 1, or remove the parameter from the configuration file.
Examples
The following examples show Next-IDs are set for a single server and for the server group environment. The default next ID block size is one.
Setting Next-ID block size for a single server
Here, consider the Next-ID block size is five.
Request ID | ARSchema.NextID |
|---|---|
1 | 5+1 |
2 | 5+1 |
3 | 5+1 |
4 | 5+1 |
5 | 5+5 +1 |
N | Previous Next ID+5+1 |
The value of the Next ID is updated when the fifth Request ID is generated.
Setting Next-ID block size for a server group environment
Here, consider a server group environment with two servers and the Next ID block size is100.
Server | Request ID range | ARSchema.NextID |
|---|---|---|
Server 1 | 1 to 100 | 100+1 |
Server 2 | 101 to 200 | 200+1 |
Consider the following scenario when 100 entries are created on Server 1. | ||
Server 1 | 201 to 300 | 300+1 |
Consider the following scenario when 100 entries are created on Server 2. | ||
Server 2 | 301 to 400 | 400+1 |
On Server 1, entries are created up to 100. After the 100th entry, 100 is added to the Next-ID size. On Server 2, entries are created up to 200. After the 200th entry, 100 is added to the Next-ID size.
Related topic