# Limit-data-in-thread-to-1-for-probe-sending-results-on-SaaS_688996331
## Background

- From the multi-customer data-in performance testing result, we learnt that the best practice is to expose only 1 data-in thread for probe sending results for each customer on SaaS. While for on-premises deployments, there's no need to limit the data-in threads, and we can't have 2 different values for the same setting for both on-premises and SaaS deployments, so we need to manually modify the data-in threads value to keep only 1 thread for probe sending results on SaaS.
- Related settings
	- **[global.thread.limit.com](http://global.thread.limit.com/).hp.ucmdb.reconciliation.datain.manager.DataInManagerFactory** (total data-in threads at global level)
		- **appilog.collectors.ResultProcessingThreadsNumber** (Percentage of threads for probe sending results at global level)
- Data-in threads for probe sending results = total data-in threads \* Percentage of threads for probe sending results

## Persona

SaaS Operations Team

## Prerequirest

SaaS CMS is on 2022.11 or later

## Steps

1. Access JMX Console as provider customer admin: **https://<cms host>/jmx-console**
2. Locate and invoke the **setGlobalSettingValue** JMX method with the following parameters values:
	| Parameter | Value |
	| --- | --- |
	| **name** | **[global.thread.limit.com](http://global.thread.limit.com/).hp.ucmdb.reconciliation.datain.manager.DataInManagerFactory** |
	| **value** | **2** |
	  
	**Important:** To limit data-in thread to 1 for probe sending results purpose only, we need to enter **2** here, as another thread is a reserved one.
3. Locate and invoke the **showSettingsByCategory** JMX method to verify the value of **[global.thread.limit.com](http://global.thread.limit.com/).hp.ucmdb.reconciliation.datain.manager.DataInManagerFactory** changes to **2.**
4. Locate and invoke the **setGlobalSettingValue** JMX method with the following parameters values:
	| Parameter | Value |
	| --- | --- |
	| **name** | **appilog.collectors.ResultProcessingThreadsNumber** |
	| **value** | **50** (in percentage)  **Note:** This value indicates percentage of total threads for probe result sending purpose. In this case, 50 is 50% of the total threads (2 in our case), that is, we have 1 thread only for probe result sending purpose. |
5. Locate and invoke the **showSettingsByCategory** JMX method to verify the value of **appilog.collectors.ResultProcessingThreadsNumber** changes to **50.**
6. Restart UCMDB Server for the two settings to take effect.