Umbraco Cloud: Is it wise/recommended to throttle .NET application to prevent overages / restarts of application?

Questions
, ,
1

Hi all,

We have Umbraco Cloud platforms that vary from v13 to v17. We’re running into issues where we use too many resources for an extended amount of time and we notice that there are unwanted and unexpected restarts of the platform.

I know that for every price tier (starter, standard, professional and enterprise) there are other boundaries on how much resources you use and how long you use too many resources. I also know that dedicated resources are a thing and we’ve recommended using these dedicated resources to our current and new clients.

I know by default .NET applications use the available resources to finish processes as quickly as possible. In a shared resource environment, this can cause high CPU situations as multiple applications can simultaneously use a lot of CPU to finish certain tasks.

I have a few questions:

  • Would it be wise to throttle .NET to use a certain percentage of the available resources?
  • Would that cause Umbraco to not restart the application if you use too many resources for a certain amount of time?
  • How do you see the role of the Cloud subscription level (starter, standard, professional or enterprise) and if it’s dedicated resources or not?

Any recommendations, guidance or other experiences would be very welcome here.

Thanks in advance for all your help.

Kind regards,

Jos Raedts

2

Hi @JosRaedts

I also have multiple clients using Umbraco Cloud and experienced the same issues as you when running on shared resource. In scenarios where I found the compute becoming exhaused the issues normally fell into either an issue with the code itself or under-resourced sites that are complex in nature or have high traffic volumes.

To answer your questions I wouldn’t recommend looking to throttle the application if possible as you’ll end up moving the problem as requests will begin to queue up or timeout completely in periods of high usage.

The first port of call I would suggest is reviewing the code and see what is actually causing the high CPU usage i.e. long running tasks, intensive operations, or just in-efficencies within code. If your code looks good then perhaps it’s a provisioning issue and you should be looking toward dedicated resource.

In-terms of viewing the currently subscription and if it’s on dedicated resource you can see this within the summary under the overview section for each project.

Hope this helps! :slight_smile: