Best Practices for B2C Commerce sandboxes

Best practices are as follows:

• Use only a small set of sites and a subset of products.
• Sandboxes are meant for unit testing -- code, not data. For more information, please see B2C Instances.
• Only install cartridges you are currently developing or testing.
• Avoid keeping all your sites on a single sandbox.
• Upload as little data as possible. This includes products, customers, inventory, prices, categories, etc.
• Avoid running concurrent tasks, like jobs in parallel.
• Delete outdated data, like source code versions.
• Minimize your locales. Too many locales can dramatically inflate job activity when multiple promotions are active.
• Use a sandbox from a POD located in or near your own region to avoid automated system-related tasks that run when you are online.
• Disable unnecessary jobs, like regular product index rebuilds when no products have been changed.
• Disable incremental indexing if not really needed.
• Disable scheduled rebuilds, or plan them outside your working hours.
• Enable Storefront Password Protection to prevent unwanted storefront traffic.
• Limit the use of a single sandbox to a single developer.
• Disconnect UX Studio pipeline or script debugger when no longer in use.
• Run a DBINIT and clear all static files once a project is completed.
• Limit changes on Production while a sandbox is being created or refreshed.