System Performance 
System performance is an important consideration when you are finding objects in classes. However, there are no hard and fast rules for achieving the best response times. You constantly need to work out a compromise between getting the most out of the functionality and maintaining system performance.
The factors that influence system performance are described below:
Load on database server
Only use your database server as a database server. Run any batch jobs or other mass-processing functions on an application server.
Characteristic value statistics
If frequent changes are made to your object assignments, we advise you to get the system to generate value statistics. For more information, see Creating Value Statistics .
It is not possible to say exactly how often you should do this. However, if you are having runtime problems, or if you have the impression that response times are getting longer, we advise you to create value statistics as a first step to solving the problem.
NoteThe data storage concept you use does not affect system performance. The assigned value data produced when you classify an object is stored independently of the classes. This is advantageous for the multiple classification of objects.
Definition of allowed values
The more values you define as allowed when you maintain the characteristic, the heavier the load on the system when you retrieve or process this information when finding objects.
Multiple-value characteristics
If multiple values are allowed for a characteristic, the load on the system is greater in order to read these values.
Interval values
We advise you to allow interval values for characteristics only where it is really necessary. If you start the find objects function with a characteristic for which interval values are allowed, for example, it is not possible to target reading of the database. All assignment records for this characteristic must be read sequentially.
Case-sensitive characteristics
If you use case-sensitive, alphanumeric characteristic in your search, avoid using the text search option (finding via a character string).
Characteristics maintained globally
Theoretically, there are two extremes:
In each class, only characteristics created especially for this class are used.
This situation is good for runtimes, but does not take advantage of global characteristics maintenance. For example, if you maintain multiple classifications of an object, you can no longer ensure that the object always has the same value assigned to the same characteristic within a class.
The characteristics are used in all classes.
This situation takes full advantage of global characteristics maintenance, but the response times for finding objects could be too long to be useful. When you first start the search, all values assigned to a characteristic are read, regardless of the class.
It is up to you how many classes you use your characteristics in. Important points to consider are how many objects in total are assigned to classes with the same characteristic, and how selective are the values assigned to objects (see Search Criteria below). A characteristic that has few allowed values and is used in a large number of classes is not selective.
Using reference characteristics only (dummy class)
This constellation cannot access the database directly to read the assignment records. All classified objects are processed sequentially.
Number of assignments to each class
The number of objects assigned to a class makes no difference if the objects have different characteristic values (see Search Criteria below), so that the list of objects produced from the search criteria is not too long.
Quality of search criteria
Finding objects without restricting the search criteria can take a long time. The response time is only limited by the number of characteristics and the number of objects assigned to the class. Wide intervals as search criteria can have a similar effect.
To limit the size of the hit list, thereby ensuring good response times, you need to run a qualified search in the SAP system. On the value assignment screen for finding objects, assign values to as many characteristics as possible.
Selectivity of values assigned to individual characteristics
The more different values are assigned to objects for a characteristic, the higher the selectivity. High selectivity is a prerequisite for good response times.
Characteristics that have only two possible values, such as Yes/No, are not very selective.
Displaying objects with no value for a characteristic
We advise you not to activate this function, except in exceptional circumstances, because the load on the system for finding these objects is heavier.
Number of sorted columns in the search result
The more columns in the result you decide to sort by, the heavier the system load for doing the sorting.