Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Configuration Management System (CMS)2018.05

Use > Sizing > Sizing Reference for Automated Service Modeling > Scenario 1. Service Discovery Only

Scenario 1. Service Discovery Only

This chapter describes the scenario that you run Service Discovery only.

Objectives

The following table lists the expected time to complete all service discoveries based on the data we collected in performance tests.

Number of Services	First Run of Service Discovery	Scheduled Rerun of Service Discovery
<100	<4 hours	<4 hours
<500	<12 hours	<12 hours

Note Scheduled Rerun of Service Discovery means rerun all service discoveries on a periodic basis, and the interval can be adjusted.

Test Environment

The performance tests are performed on an environment that meets the following preconditions:

One service consists of less than 30 Running Software instances, which run on different hosts.
One host can be discovered by the Host Discovery by Shell job within two minutes if everything works as expected.

Note

If the actual environment cannot meet these preconditions, the Service Discovery performance may not reach the above objectives. In this case, you can adjust several configuration settings to improve the Service Discovery performance.
There is no CI and Relationship discovered by Universal Discovery.

The numbers of CIs and Relationships reported by Service Discovery are shown in the table below.

CI Types	100 Services	500 Services
Node	6000	30000
IP Address	6000	30000
J2EE Domain	6000	30000
Running Software	12000	60000
J2EE Application	6000	30000
Service Connection Point	6000	30000
IP Service Endpoint	6000	30000
Consumer-Provider Link	12000	60000
Composition Link	18000	90000
Membership Link	6000	30000
Ownership Link	12000	60000
Usage Link	6000	30000

Configurations

This section lists the hardware and configuration settings that we used in performance tests. The real numbers may vary depending on the actual environment.

Infrastructure

The following table lists the configurations we used in performance tests for the scenario of Service Discovery only. They have been verified in testing environment and should be regarded as minimum conditions for Service Discovery only environment.

Role	CPU	RAM
UCMDB Server	8 Cores	32 GB
Data Flow Probe	8 Cores	16 GB
Database	8 Cores	32 GB

In an environment that has lower hardware configurations, the following results may occur:

High CPU and memory usage
Service Discovery cannot finish within the expected time

JVM Heap Size

The following table lists the JVM heap size configurations used in the performance tests.

It is recommended that you make sure the environment meets the following configurations before you run Service Discovery.

Role	-Xms	-Xmx
UCMDB Server	4096 MB	8192 MB
Data Flow Probe	2048 MB	4096 MB

You can adjust the JVM heap size in the following manner:

For UCMDB server, set the wrapper.java.maxmemory parameter in the <UCMDB_Server_Home>\bin\wrapper-platform.conf file.
For Data Flow Probe, set the set.GATEWAY_MAX_MEM and set.MANAGER_MAX_MEM parameters in the <DataFlowProbe_Home>\bin\WrapperEnv.conf file. For more information, see the Data Flow Management section of the UCMDB Help.

Job Execution Threads

By default, the thread pool size on the Data Flow Probe is 80. Increasing this parameter can improve the Service Discovery performance, but will increase the workload on the Data Flow Probe. If you need to run a large number of service discoveries, you can increase this parameter accordingly.

The following table lists the thread distribution used in the performance tests, and we increased the thread pool size to 120.

Job Name	Number of Threads
Business Element Resolver	8
Host Discovery by Shell	64
Running Software Dependencies	16

You can adjust the thread pool size by setting the appilog.agent.local.services.poolThreads parameter in the DataFlowProbe.properties file. For more information, refer to the Data Flow Management section of the UCMDB Help.

Send Help Center feedback