---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Optimizing data collection

# Optimizing data collection {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The optimized Performance Analytics data collector reduces the time, memory, and CPU usage
for processing large data sets.

The optimized data collector is active by default on all instances
starting in Tokyo. It is activated upon upgrading.
To
deactivate the optimized collector, create the system property
com.snc.pa.dc.hsql and set it to <kbd class="ph userinput">false</kbd>. For more
information, see [Add a system property](https://www.servicenow.com/docs/access?context=r_AvailableSystemProperties&version=xanadu&pubname=xanadu-platform-administration&section=t_AddAPropertyUsingSysPropsList&ft:locale=en-US).  
Important:  
Oracle databases are not supported. Other instances that still use the Performance Analytics Scores \[pa_scores\] table are also not supported. The optimized data collector supports only instances where the indicator scores are on the two tables Scores Level 1 \[pa_scores_l1\] and Scores Level 2 \[pa_scores_l2\]. For more information, see [Migrating Performance Analytics scores](https://servicenow-prod.fluidtopics.net/LRXUAN2daUTQNI22NG240Q#pa-scores-migration "The Performance Analytics Scores [pa_scores] table was split into two tables. This structure helps with processing large numbers of scores. You can migrate your scores from the old table structure to the new, using the score migration tool.").

The optimized data collector supports the following capabilities:  
* Ability to handle over 10 million records without adverse impact to performance.
* Support for at least 10 breakdowns with breakdown matrix enabled. Breakdown support includes:
  * Dot-walked conditions
  * Two large breakdowns, with up to 1 million records
  * Breakdown relations
  {#optimized-data-collection__ul_e2s_npd_4qb}
* Support for additional conditions on indicators and breakdowns.
* Optimizations for Count Distinct aggregation.
{#optimized-data-collection__ul_dwm_bnd_4qb}  
Note:  
The default maximum number of records allowed per indicator source for data collection has been increased for optimized data collection. For more information, see the com.snc.pa.dc.hsql.max_row_count_indicator_source property in [Performance Analytics properties](https://servicenow-prod.fluidtopics.net/IVnMVeOkRJigpD5jDVKkCQ "These system properties control the behavior of Performance Analytics.").

The optimizations stem from the use of an embedded database. A standard data collection job
stores all scores in the node memory during the job. However, an optimized data collection job
moves packets of scores to temporary storage on disk. At the end of the job, the scores are
written to the scores tables and the temporary database is cleared.  
Note:  
Memory optimization using lazy loading has been implemented to eliminate out-of-memory errors. However, this memory optimization could increase CPU usage and lengthen processing time for large jobs. For more information, contact Customer Service and Support.