Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8529681
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 11, 20262026-06-11T09:05:10+00:00 2026-06-11T09:05:10+00:00

I am building an Azure Web Role that will need to invoke a lot

  • 0

I am building an Azure Web Role that will need to invoke a lot of external web services.

I remember for ASP.Net 1.1, there was a default maxconnection limit of 2, which you could adjust if your application needed more than that (which was pretty low, let’s be honest). On ASP.Net 2.0, I believe they raised this, and the recommendation was 12 times the number of cores.

What are the limits, and the means of adjusting this, on Azure Web Roles? I will have hundreds, or thousands, of concurrent outbound requests going at once. Does this mean that I need bigger instances (more cores), or can I do this by using more “Extra Small” instances and configuring them correctly (even if that means 12 per server)?

Thank you.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-11T09:05:11+00:00Added an answer on June 11, 2026 at 9:05 am

    The size of your instance will only determine the bandwidth that will be reserved for your instance (XS is 5 Mbps, more info here). What you’ll need to do is simply change the DefaultConnectionLimit to more than 2:

      <system.net>
        <connectionManagement>
          <add address="*" maxconnection="12"/>
        </connectionManagement>
      </system.net>
    

    Add this to your web.config if you want to allow this in your web application. Add the following to your WebRole.cs if you want to invoke services before starting your instance for example:

        public override bool OnStart()
        {
            ServicePointManager.DefaultConnectionLimit = 12;
            return base.OnStart();
        }
    

    Keep in mind that, even if the requests are queued, you’ll get a better overall performance if you call the webservices in an asynchronous way. Here is a very basic example (assuming you call a simple REST service, WCF client proxies have better support for asynchronous requests):

    <%@ Page Async="true" ... %>
    
    public partial class AsyncPage : System.Web.UI.Page
    {
        private WebRequest req;
    
        void Page_Load (object sender, EventArgs e)
        {
            AddOnPreRenderCompleteAsync (
                new BeginEventHandler(BeginWebServiceCall),
                new EndEventHandler (EndWebServiceCall)
            );
        }
    
        IAsyncResult BeginWebServiceCall (object sender, EventArgs e, 
            AsyncCallback cb, object state)
        {
            req = WebRequest.Create("http://some.webs.service/rest/api");
            return req.BeginGetResponse (cb, state);
        }
        void EndWebServiceCall (IAsyncResult ar)
        {
            using (var response = req.EndGetResponse(ar))
            {
                using var reader = 
                    new StreamReader(response.GetResponseStream()))
                {
                    var text = reader.ReadToEnd();
            ...
                }
            }
        }
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm building an asp.net application that will be deployed on Azure. For the moment,
I am building an ASP.NET MVC 3 app which will run in Azure. Everything
Building a simple asp.net web app just to test things out (will obviously refactor
Does anyone have any links for building RESTful web services with the ASP.NET Web
Building a new ASP.net application, and planning to separate DB, 'service' tier and Web/UI
I'm currently building an Azure Web Role. I am testing this project against a
I have a web app that I'm building. It uses 3 different web services
I'm currently in the process of building our ASP.NET C# 3.5 Web site and
Azure, probably ASP.NET Webforms. We're building a management interface for about 8 tables. Usual
building a site using PHP and MySQL that needs to store a lot of

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.