Web Site Really Slow

We are currently trying to cut our website over to a new server running
Windows 2003 Web Edition
with IIS 6.0

The same website (PRODUCTION) is on a Windows 2000 Advanced Server box
running IIS 5.0

The production site seems to be MUCH faster. There are certain pages I go
to that come up within seconds. ON the New server the same page takes near
a minute to come up?

Just wondering if there are any differences I need to look for in the
Windows 2003 environment?

george
Wed Oct 29 09:04:56 CST 2003

I should also say the site is using ASP with a ACCESS DB for it's backend
currently
Future plans to migrate to SQL Server


"george" <geo_rob713@yahoo.com> wrote in message
news:etcLn1inDHA.3024@tk2msftngp13.phx.gbl...
> We are currently trying to cut our website over to a new server running
> Windows 2003 Web Edition
> with IIS 6.0
>
> The same website (PRODUCTION) is on a Windows 2000 Advanced Server box
> running IIS 5.0
>
> The production site seems to be MUCH faster. There are certain pages I go
> to that come up within seconds. ON the New server the same page takes
near
> a minute to come up?
>
> Just wondering if there are any differences I need to look for in the
> Windows 2003 environment?
>
>

Kristofer
Wed Oct 29 09:22:51 CST 2003

Hello,

Is it the same the next time you access the very same file? It is possible
that pages are not cached yet, and therefore the pages gets loaded slower,
but on the production machine, they are cached. But a minute sounds quite
much. It happens to all webpages? Is this ASP.NET? I would enable tracing,
and see what is taking so much time. You can find more about this here:

http://www.asp.net/Tutorials/quickstart.aspx
(find the Tracing section in the left pane)

--
Regards,
Kristofer Gafvert - IIS MVP
http://www.ilopia.com - FAQ & Tutorials for Windows Server 2003, and SQL
Server 2000
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.

Problems with spam and viruses? See
http://www.ilopia.com/security/newsposting.aspx


"george" <geo_rob713@yahoo.com> wrote in message
news:etcLn1inDHA.3024@tk2msftngp13.phx.gbl...
> We are currently trying to cut our website over to a new server running
> Windows 2003 Web Edition
> with IIS 6.0
>
> The same website (PRODUCTION) is on a Windows 2000 Advanced Server box
> running IIS 5.0
>
> The production site seems to be MUCH faster. There are certain pages I go
> to that come up within seconds. ON the New server the same page takes
near
> a minute to come up?
>
> Just wondering if there are any differences I need to look for in the
> Windows 2003 environment?
>
>

george
Wed Oct 29 09:31:37 CST 2003

Thanks, I'll check it out.

No it isn't ASP.NET It happens on some pages not all.
Mainly the pages that are doing a lot or grabbing a lot from the DB.
Maybe not a minute but it is a significant amount of time that I do not
experience on the IIS 5.0 server.

I did test it locally seemed to be fine. Now we moved it to our ISP
same ISP hosting the old site. I'm not getting no where near the same
performance as the old site is now.

I'm also noticing a few posts on what seems to be similar issues.

Again thanks for your help.


"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
news:ugAFFCjnDHA.2772@TK2MSFTNGP12.phx.gbl...
> Hello,
>
> Is it the same the next time you access the very same file? It is possible
> that pages are not cached yet, and therefore the pages gets loaded slower,
> but on the production machine, they are cached. But a minute sounds quite
> much. It happens to all webpages? Is this ASP.NET? I would enable tracing,
> and see what is taking so much time. You can find more about this here:
>
> http://www.asp.net/Tutorials/quickstart.aspx
> (find the Tracing section in the left pane)
>
> --
> Regards,
> Kristofer Gafvert - IIS MVP
> http://www.ilopia.com - FAQ & Tutorials for Windows Server 2003, and SQL
> Server 2000
> Reply to newsgroup only. Remove NEWS if you must reply by email, but
please
> do not.
>
> Problems with spam and viruses? See
> http://www.ilopia.com/security/newsposting.aspx
>
>
> "george" <geo_rob713@yahoo.com> wrote in message
> news:etcLn1inDHA.3024@tk2msftngp13.phx.gbl...
> > We are currently trying to cut our website over to a new server running
> > Windows 2003 Web Edition
> > with IIS 6.0
> >
> > The same website (PRODUCTION) is on a Windows 2000 Advanced Server box
> > running IIS 5.0
> >
> > The production site seems to be MUCH faster. There are certain pages I
go
> > to that come up within seconds. ON the New server the same page takes
> near
> > a minute to come up?
> >
> > Just wondering if there are any differences I need to look for in the
> > Windows 2003 environment?
> >
> >
>
>

bbooth
Wed Oct 29 12:30:05 CST 2003

George,

It is very difficult to nail down this type of problem with conventional
troubleshooting methods. There are so many possible (yet unobvious) reasons
for performance woes. From experience I would guess that the OS version
probably has nothing to do with the problem or even with all those *other*
IIS6 performance issues that people have reported. The easiest thing to do
here is to get some memory dumps of IIS as you request your slow pages.
There is usually only a single bottleneck in the code execution which can
be spotted in such a memory dump.

I recommend downloading IISSTATE to get the memory dumps. If you go this
route *be sure* you read *all* of the available documentation otherwise the
chances are good you won't get the required information. To give you a
head-start what you'll want to do is take the dumps as if you were
experiencing a hang. In other words, request a page that you know goes too
slow then get a memory dump *before* the page finishes. Do this a few
separate times. Pretty soon you'll see a distinct pattern in the iisstate
output that will tell you where the problem is. Once you get the few sets
of dumps feel free to post the output here. If you haven't looked at a
couple hundred memory dumps of IIS then it might not be so obvious as to
what the output is telling you.

http://www.iisfaq.com/iisstate

Thanks,
Brian Murphy-Booth

george
Wed Oct 29 13:38:50 CST 2003



Thanks Brian for the info. Your right I haven't been exposed to this. But
thanks
for the info. Our ISP is going to try moving the box outside the new
firewall
and then we will test it just to see if it is the new firewall or not. I
guess the
old server was not behind this same firewall. So that is one thing we are
going
to look at. I'll check out the site you sent.

Thanks,
George


"Brian Murphy-Booth" <bbooth@online.microsoft.com> wrote in message
news:ZKA8wqknDHA.1548@cpmsftngxa06.phx.gbl...
> George,
>
> It is very difficult to nail down this type of problem with conventional
> troubleshooting methods. There are so many possible (yet unobvious)
reasons
> for performance woes. From experience I would guess that the OS version
> probably has nothing to do with the problem or even with all those *other*
> IIS6 performance issues that people have reported. The easiest thing to do
> here is to get some memory dumps of IIS as you request your slow pages.
> There is usually only a single bottleneck in the code execution which can
> be spotted in such a memory dump.
>
> I recommend downloading IISSTATE to get the memory dumps. If you go this
> route *be sure* you read *all* of the available documentation otherwise
the
> chances are good you won't get the required information. To give you a
> head-start what you'll want to do is take the dumps as if you were
> experiencing a hang. In other words, request a page that you know goes too
> slow then get a memory dump *before* the page finishes. Do this a few
> separate times. Pretty soon you'll see a distinct pattern in the iisstate
> output that will tell you where the problem is. Once you get the few sets
> of dumps feel free to post the output here. If you haven't looked at a
> couple hundred memory dumps of IIS then it might not be so obvious as to
> what the output is telling you.
>
> http://www.iisfaq.com/iisstate
>
> Thanks,
> Brian Murphy-Booth
>