Re: How well will IIS scale up
From: John Timney \(Microsoft MVP\) (timneyj_at_despammed.com)
Date: 09/23/04
- Next message: dave v: "OracleException Deserialization"
- Previous message: Scotter: "HELP PLEASE - need app to modify multiple MDB table designs simultaneously"
- In reply to: Guess: "Re: How well will IIS scale up"
- Next in thread: Guess: "Re: How well will IIS scale up"
- Reply: Guess: "Re: How well will IIS scale up"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 23 Sep 2004 21:46:14 +0100
IIS can scale a server farm to a massive level, so technically it could
scale out to whatever your requriements are - but with scale out comes
expense. This is where you have to consider how your app is architected,
and if your propsed design is appropriate.
-- Regards John Timney Microsoft Regional Director Microsoft MVP "Guess" <intrader@aol.com> wrote in message news:MPG.1bbc1c4858fb50a39896b0@news-server.socal.rr.com... > [This followup was posted to microsoft.public.dotnet.general and a copy > was sent to the cited author.] > > In article <ultOYqAoEHA.3896@TK2MSFTNGP15.phx.gbl>, "John Timney > \(Microsoft MVP\)" <timneyj@despammed.com> says... > > It all come down to how you scale your arhcitecture. You need to work out > > your expected hit rate, and get some load testing software and simulate your > > hits. When the server falls over with server 500 messages you have exceeded > > your maximum hits. If it is greater than your expected hit rate then you > > need to scale out or up, or rework your application. > > > > -- > > Regards > > > > John Timney > > Microsoft Regional Director > > Microsoft MVP > > > > > > > > "Guess" <intrader@aol.com> wrote in message > > news:MPG.1bb966df15db85b19896af@news-server.socal.rr.com... > > > The situation is as follows: > > > 1. I would like to serve a web page that takes considerable time to > > > process. > > > 2. While the page is processing, the client displays an appropriate wait > > > message. > > > > > > What are the consequences of having this long processing page when there > > > are many simultaneous requests from many clients for the same page (say > > > 75+). > > > > > > I appreciate any opinions or suggestions. > > > > > > Thanks > > > > > > [This followup was posted to microsoft.public.dotnet.general and a copy > > > was sent to the cited author.] > > > > > > > > > > Thanks for your thoughts! > > So, you are saying that IIS is capable holding a large number of waiting > threads?. The processes that I plan to wait for a Web Services running > on some other farm of servers. > I am thinking of using BigIP to manage the farm of IIS boxes, as well as > another BigIP box to manage the farm of Web Services handlers. When the > number of requests is not over a threshold, we will process by letting > the thread wait for the Web Service response before responding to the > client. > If however, the number of requests is over the thresshold, we will make > an appropriate entry in a database, and immediatelly return to the > client. The processing will still be done, but now instigated by some > process in SQL Server that will interact with the Web Service.
- Next message: dave v: "OracleException Deserialization"
- Previous message: Scotter: "HELP PLEASE - need app to modify multiple MDB table designs simultaneously"
- In reply to: Guess: "Re: How well will IIS scale up"
- Next in thread: Guess: "Re: How well will IIS scale up"
- Reply: Guess: "Re: How well will IIS scale up"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
