Re: Desperate Help Needed
From: David Morgan (david_at_davidmorgan.me.uk)
Date: 04/12/04
- Next message: SM: "Re: IISState log interpret"
- Previous message: Arif: "Re: redirect http to https for virtual directories"
- In reply to: David Wang [Msft]: "Re: Desperate Help Needed"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Apr 2004 17:23:06 +0100
Hi David
Firstly, thanks for your reply.
In some cases the pages do return a lot of results, but not more than a few
hundred K of output HTML. I am aware that enable buffering is important in
helping performance, but it _reduces_ the problematic pages, not "makes
worse".
The queries take no time at all to execute, it is the sending the data to
the client that takes the time and in some cases fails. As we are not
buffering we can see this as the header HTML is received then the problem
occurs. All queries are executed before any HTML and we use GetRows then
destroy everything.
Something is wrong, I know it is, but I don't know where. Have been using
ASP for years with big pages.
What do you mean about the DoS vulnerability. Is something checking for
this within Windows? Maybe our ISP has something. How would something like
this work with a file download over HTTP? Surely the network traffic would
appear the same.
Regards
David
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:Oazx3DIIEHA.2924@TK2MSFTNGP09.phx.gbl...
> How large are the pages generated by ASP, and what are the page's
> performance metrics?
>
> If you are making database queries or returning large results, then you
> certainly should not use "Response.Buffer = true" since that feature
> basically buffers all the output on the server and then send it in one go.
> If the data is several megabytes, this will be very problematic on the
> server (potential DoS vulnerability) as well as network.
>
> Also, if your ASP pages make queries or just take a long-time to execute,
> that can also hang the server or cause clients to drop the connection.
>
> I think you've basically got pages that behave poorly -- either send back
> lots of data or takes a long time to execute -- and this exacerbates
network
> situations to the point that they seem random to you. In other words --
> pages failing to load is usually a problem with your pages, and if you do
> not properly optimize your pages for performance, you will see such
failures
> as a consequence. Since your pages seem to traffic in a lot of data, I
> suggest you sit down and think about what your pages are doing and make
sure
> it makes sense performance-wise and also scales. This is not going to be
an
> easy band-aid since there is no magic pixie dust to sprinkle to make
things
> magically faster or more scalable.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "David Morgan" <david@davidmorgan.me.uk> wrote in message
> news:eIzvsaBIEHA.3968@TK2MSFTNGP12.phx.gbl...
> Hi
>
> Periodically users of my website report that pages fail to load fully.
They
> only receive partial amounts of the full ASP generated HTML.
>
> In most cases this causes the page not to render as tables are used, but
in
> Netscape etc, the pages partially render. This problem has been
experienced
> by many users on many different platforms with different browsers etc.
>
> I do not know where to start with this problem and any help would be
> gratefully received.
>
> Our server is hosted in the Netherlands and we do not really have physical
> access. Our site is getting about 10,000 hits per day and the problem
> cannot be reliably reproduced although it does seem to happen more
> frequently on laptops. I think that load on the server/network has a
> bearing on the problem but I cannot be sure.
>
> Naturally our ISP says it's nothing to do with them, but we do have some
> quite large ASP pages on our site. We also have some movie files which
some
> users, (but less than ASP), complain about not fully loading.
>
> The ASP problem was significantly reduced when we turned off enable
> buffering. Also, I have added some Response.Flush statements in some
pages
> which also appeared to help.
>
> IBM Server
> Running W2K SP3, SQL Server 2000
> 2 x Xeon Processors, 1Gb RAM, 76 Gb C RAID 1, 126Gb D RAID 5.
>
>
>
- Next message: SM: "Re: IISState log interpret"
- Previous message: Arif: "Re: redirect http to https for virtual directories"
- In reply to: David Wang [Msft]: "Re: Desperate Help Needed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
