Tip #1005: Keep your portals warm and cuddly

This week I had a privilege to sit among Australian Technical Solution Professionals (TSPs) absorbing some of the best selling techniques delivered by none other than our resident video tipster Derik Bormann.

One of challenges of the pre-sales demos is that they need to flow as smooth as butter – there is no room for mistakes and any hiccup is nearly fatal. “You had your chance” seems to be the motto.

When demoing Microsoft Portals, the performance needs to be especially flawless – expectations are high and there is no room for an hourglass cursor. Instead of frantically refreshing the pages 5 minutes before the demo, why not to keep your portal ready to go by hitting the pages you’re about to demo every minute or so, starting 15 minutes before your demo.

If you already use external monitoring services like https://pingdom.com, https://nodeping.com, or any other, go ahead and add your portal pages there – done. If you don’t have any of those (and why would you if you work in pre-sales), here’s how you can create a quick and dirty warmer-upper using existing Azure subscription (I assume you do have one of those if you demo Dynamics 365 and Portals, right?)

  1. In your https://portal.azure.com click + New, search for Scheduler, then click Create.
    Azure Scheduler
  2. Give it a good name
  3. Pick up an existing job collection or create a new one. Note: you’d want a collection in standard tier or higher – free one has only hourly runs.
  4. Click Action settings, select Https Action, enter Url of your page, leave the rest as is and hit OK
    Scheduler action
  5. Click Schedule and enter the details: start date/time (say 15 minutes before the demo), end date/time (15 minutes after), frequency of 1 minute. (And no, I don’t demo at 4:30 AM, it’s UTC speak for 3:30 PM in Sydney)
    Start stop
  6. Rinse, repeat for the pages you’re going to use in your demo.

You are all set now. Whatever problem you encounter during the demo, portal performance ain’t gonna be it.

3 thoughts on “Tip #1005: Keep your portals warm and cuddly

  1. Joseph says:

    Hi , Could you please explain how this works in further detail? I understand what you are saying, but how does hitting the site keep the portal ready to go? (As opposed to just hitting it when you are ready ?) I guess what i’m asking is… how does hitting the page rapidly make it more ready than just hitting it when you need? Sorry if this is a dumb question…im new here.

    • Hi Joseph,
      there are couple reasons to keep the portals warm:

      1. Portals do not talk to CRM every time a slice of data is required. Once data is retrieved, e.g. a specific view, or even a page content, portal would keep it in cache (memory) and, if requested again, would use cache, thus bypassing data retrieval from CRM. Cache, the variety used by the portals, have an expiration period. If specific data is not requested within this period (e.g. 30 minutes), it will be removed from cache and portals will have to issue another request to CRM to fetch the data. In other words, if your site is dormant, first data retrieval is expensive and hitting your pages helps to avoid that hit.
      2. Portals run in Azure, on IIS platform. If web app is not active for a period of time, it will be unloaded from memory. The first request after that will be slow due to application being loaded into memory. Retrieving any page from the portal helps to avoid that.


  2. Bert says:

    Not Sure what issue this is trying to solve.

Leave a Reply

Your email address will not be published. Required fields are marked *