Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

prpcUtils is running slowly



The performance of the prpcUtils script is slow when importing rulesets or hotfixes, sometimes taking upwards of 15 minutes to complete the process.

Error Messages

Not applicable.

Steps to Reproduce

1) Configure and run the prpcUtils script.

Root Cause

A defect or configuration issue in the operating environment. By not specifying a constant Pega temp directory, each time prpcUtils is run it will regenerate the entire temp directory.


To Improve the performance of the prpcUtils script, make the following adjustments:

Create a copy of prconfig.xml, and be sure to specify a value for the following:
<env name="initialization/explicittempdir" value="" />

This will specify a location to be used as the explicittempdir for prpcUtils.

After updating this, save this file.

Finally, update the file, specifically the property 'pegarules.config'. Uncomment this line if it is not already and specify the location where the prconfig.xml file has just been saved.

After prpcUtils is run once, the files in the specified llocation should remain and not be regenerated each time it’s called, which should speed up the start of the engine and execution of the prpcUtils script.

Another item to consider is the location of the database in relation to where this script is being run. Ideally, this should be done from within the same datacenter.  


Published April 15, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us