Performance impact of setting search characters

Implementing search characters is an operation that changes the attribute on the GCR, and thus is a configuration change. If you issue this operation in an empty data domain, it runs quickly. If you issue this operation on an index with a large number of existing records using the Configuration Web Service, the processing of this operation can have performance impact largely caused by re-indexing.

Performance impact of this operation ( as well as other updating or configuration changing operations) consists of the following aspects:

Such operations cause re-indexing, which is associated with CPU and memory usage costs. In particular, the operation for changing an attribute on the GCR will not finish until re-indexing is completed.
Such operations are considered updating operations, which means that no other updates can be processed until a specific update is completed (for example, all updating Web service requests will wait in the queue during this update).