Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP:
🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites

What I didn’t know is that you can also trigger warmup in your local development environment.
This can help expose bugs or issues before deploying to DXP and INT/PREP/PROD.

Example:

if (_webHostingEnvironment.IsDevelopment())
{

    services.AddCmsWarmup(configure =>
    {
        configure.Disable = false;
        configure.FollowLinkLevel = 10; // Should cover most pages?
        configure.WaitingForStartupTimeout = TimeSpan.FromSeconds(180);
        configure.StartupWaitingInterval = TimeSpan.FromMilliseconds(10);
        configure.RequestTimeout = TimeSpan.FromMinutes(1);
        configure.MaxNumberParallelRequests = 10; // Increase to speed up warmup and simulate more load
        configure.AdditionalPaths.Add("/en/alloy-plan"); // Add path to warmup that crawling won't find following links                    
    });

...

Note: .AddCmsWarmup() is already implicitly triggered when using .AddCmsCloudPlatformSupport(). However, for reasons I won’t go into here, it’s not something you trigger in your local/development environment.