Azure Server Spec Question

Newapl21 6 Reputation points

We're trying to setup a .NET development/test environment. Usually we have onsite local servers which always has atleast 4GB Memory( RAM) even for development systems. Because as a admin we're always told to leave atleast 2 GB for OS and then remaining memory to use for other application services. Now we're trying to get a low end development environment on azure and it seems the memory(RAM) starts ast 1GB and goes up with .5 GB. I understand that working with Linux /Unix systems the memory utilization is more efficient. But personally couldn't say that about windows from my experience.
So with the snapshot attached, would it be ok to select 1GB ram or so for dev/test environment without crashing and getting really poor performance due to paging or other congestion on the system? We want to see atleast some reasonably good response during small /minimal load testing.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,206 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Takahito Iwasa 4,841 Reputation points MVP


    Free and Shared plans have a quota limit on resources.

    From this, in my experience, it is desirable to select a more suitable plan (Basic or higher) when performing load tests and measuring performance.

    0 comments No comments

  2. ajkuma 23,826 Reputation points Microsoft Employee

    Newapl21-8123, As TakahitoIwasa mentioned, you may leverage Basic or higher plan based on your requirement for testing. Off course, as shared tiers are intended for testing/deployment, you can always start by leveraging F1, D1 and then switch to B1 tier.

    The F1 and D1 hosting plans are base tiers that run on the same Azure VMs as other App Service apps. Some apps might belong to other customers, and they have quota limits. Also, these tiers cannot be scaled out (add more instances) like on other higher tiers (B1 and above)

    Just to highlight further, on App Service, you could have multiple separate apps in the same App Service Plan (ASP), since you pay only for ASP, saving costs.

    As for as instances and content, the content share (%HOME%) directory contains an app's content, and application code can write to it. If an app runs on multiple instances, the %HOME% directory is shared among all instances so that all instances see the same directory. So, for example, if an app saves uploaded files to the %HOME% directory, those files are immediately available to all instances.

    The temporary local storage (%SystemDrive%\local) directory is not shared between instances, neither is it shared between the app and its Kudu (SCM) app.

    If you still have any questions on this, please just let us know we will be more than happy to assist you further.

    To benefit the community find the right answers, please do mark the post which was helpful by clicking on ‘Accept Answer’ & ‘Up-Vote’.

    0 comments No comments