# How to optimize Virto Commerce Deployment package for Production

**URL:** <https://www.virtocommerce.org/t/how-to-optimize-virto-commerce-deployment-package-for-production/405>\
**Category:** hosting\
**Tags:** great-solutions, azure\
**Created:** [December 17, 2021, 7:15am UTC](https://www.virtocommerce.org/t/how-to-optimize-virto-commerce-deployment-package-for-production/405 "2021-12-17T07:15:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![OlegoO](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/olegoo/32/27_2.png) [@OlegoO](https://www.virtocommerce.org/u/OlegoO)\
**Post date:** [December 17, 2021, 7:15am UTC](https://www.virtocommerce.org/t/how-to-optimize-virto-commerce-deployment-package-for-production/405/1 "2021-12-17T07:15:54Z")

</div>

Optimized Virto Commerce Deployment Package allows to improve startup time and build a seamless update process.

Virto Commerce and Virto Commerce CLI allow building optimized Virto Commerce Deployment Package for Production.

We recommend using these best practices.

### Step 1. Update Application Setting

Set **VirtoCommerce:RefreshProbingFolderOnStart** to **false** for Staging and Production environments.

**Note:** It prevents copying all modules dlls to app\_data from modules folder (discoverypath) and disable Distributed lock for this operation.

### Step 2. Modify CI Process

When you create a new package, add Virto Commerce CLI (vc-build) command to copy modules to `app_data/modules` during CLI process.

```auto
vc-build initplatform -probingpath ./platform/app_data/modules -discoverypath ./platform/modules

```

**Note:** The command will apply the operation of the package with the correct **app\_data/modules folder** and improve startup time on Virto Commerce.

### Step 3. Deploy a new package to the environment

### Step 4. Start The Environment