Re: major iis5 asp performance problems
From: tparks69 (tparks69_at_discussions.microsoft.com)
Date: 07/22/04
- Next message: Kristofer Gafvert: "Re: homepage redirects itself"
- Previous message: Team Macromedia: "Re: IIS Hack : Anyone explain cause..."
- In reply to: David Wang [Msft]: "Re: major iis5 asp performance problems"
- Next in thread: Bjorn S: "Re: major iis5 asp performance problems"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Jul 2004 10:16:02 -0700
Ah, yes, why did we architect things this way? First of all we have two sets of users for the app. The first set of users is on our LAN. They use IE to browse the app and hit a central web server for the pages like you would expect.
The second set of users use laptop computers that have a 9.6k wireless connection to our network. This is too slow to serve them pages from a central web server. So, we just put IIS directly on the laptops and run the pages locally. We use XML messages to post the user data from the laptops over the 9.6k wireless connection to our centralized SQL Server.
Once we get a broadband quality wireless connection, we'll be able to serve this second set of users as we do the first set, from our central web server. But, a VB app on the laptops would have been twice as much development since we already had the app running on the LAN.
Tom
"David Wang [Msft]" wrote:
> Use IIS State on the bad dllhost/inetinfo.exe during the 30+ seconds it
> takes to load, and post the log here. Let's see what is going on inside that
> dllhost.exe...
>
> http://www.iisfaq.com/default.aspx?view=P197
>
>
> Right now, it sounds like on the bad machines that you run out of physical
> memory and dip into virtual memory, at which point hard-drive thrashes and
> performance goes out the window. Since you only have 128MB in the machine
> and the OS took about half of that, if any app gets over 50-60MB, things are
> going to thrash badly and weird things can happen. So, interesting question
> is why the app gets to 50-60MB (whether it is actually expected or not).
>
>
> It's not certain to me why you run a web app on many isolated web servers --
> seems like the Internet is all about running ONE web server with many
> light-weight clients -- so you only need more RAM for that one web server
> and not 2000 clients. If the web app is *meant* to be stand-alone, then that
> is very, very weird. You can probably do better with a simple stand-alone
> VB program to stitch the VB/COM calls together with a superior UI in very
> little time.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "tparks69" <tparks69@discussions.microsoft.com> wrote in message
> news:CC85CE31-1515-4D2D-B348-A579E122F079@microsoft.com...
> I know we need more RAM its just a matter of how to get more RAM for 2000
> computers! We don't have the money or manpower right now to upgrade.
>
> Besides the app runs fine on most of the computers, its just some of them
> have this problem, so I'm thinking there must be an issue with some
> configuration setting somewhere.
>
> Tom
>
> "Paul Lynch" wrote:
>
> > On Tue, 20 Jul 2004 12:58:01 -0700, "tparks69"
> > <tparks69@discussions.microsoft.com> wrote:
> >
> > >OK we have a set of laptop computers each running IIS5. Every laptop is
> a virtual clone of each other. We have a web app running on the localhost
> on each laptop. On most of the laptops, the response time between ASP pages
> is in the 1 second range. On other machines, the response time is
> terrible... in 30+ seconds per page (I've heard up to 6 minutes per page
> from users).
> > >
> > >When I watch the inetinfo and dllhost processes in the task manager, I
> note the following differences in the bad machines vs the good ones:
> > >
> > >Good: inetinfo.exe process starts out with around 4MB of memory
> > >Bad: inetinfo.exe is only getting like 1-2MB of memory
> > >
> > >Good: dllhost starts out with around 10MB memory, goes up to 11-12MB
> when calling our VB COM+ dlls to post/process data, then goes back to 10MB
> after page loaded. (again, page loads in like 1 second)
> > >Bad: dllhost starts out with around 10MB, but shoots up to 50-60
> sometimes 80MB while processing the page. during this time the harddrive
> light is almost constantly on. (the page is taking 30+ seconds to load)
> > >
> > >I don't think the application code is the problem since on most boxes
> pages load in < 1 second. Keep in mind there is only one user at a time on
> the site as it is running local and disconnected.
> > >
> > >I have looked at:
> > >- Virtual memory settings
> > >- IIS performace tab settings
> > >- caching settings in IE
> > >- running COM+ objects in library application instead of server
> application
> > >- shutting down extraneous services to conserve memory
> > >- changing the IIS max memory settings in the registry
> > >- defragging the harddrive
> > >
> > >and more.... none of these things have helped.
> > >
> > >The environment is: Win2K Pro SP4, 128MB ram per box (we cannot upgrade
> this so don't tell me we need more RAM), IE 6.0.2800.1106 SP1, IIS5
> > >
> > >I was wondering if one of you guru's out there might have some
> suggestions... we're pretty desperate here, so any help is appreciated.
> > >
> > >Thanks!
> > >Tom
> > >
> >
> > Tom,
> >
> > Whether you like it or not you need to find a solution which includes
> > running IIS5 on machines with more than 128MB of memory. 512MB is a
> > sensible entry level for any kind of production machine.
> >
> >
> > Regards,
> >
> > Paul Lynch
> > MCSE
> >
>
>
>
- Next message: Kristofer Gafvert: "Re: homepage redirects itself"
- Previous message: Team Macromedia: "Re: IIS Hack : Anyone explain cause..."
- In reply to: David Wang [Msft]: "Re: major iis5 asp performance problems"
- Next in thread: Bjorn S: "Re: major iis5 asp performance problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|