Best way to configure a small script to run FAST!!!!

[Toni]

I've got a very small ASP.NET script running on ASP.NET 3.5. It is passed parameters
from a classical ASP (VBScript) page using XMLHTTP and a value is returned. So far, it
look like this:

<%@ Page Language="VB" %>
<%
response.ContentType="text/HTML"
dim strData
strData = Request.Form("invar")
Response.write (value calculated from "invar")
%>

While this seems small, I really need this to execute with as little overhead as
possible - right now, the first time I call any ASP.NET script on my server (even "Hello
World"), there is a 4 second long delay and I don't know why!

Can anyone tell me how I can get this script to execute with as little over overhead as
possible, and eliminate that 4 second delay???

 

[Registered User]

I've got a very small ASP.NET script running on ASP.NET 3.5. It is passed parameters
from a classical ASP (VBScript) page using XMLHTTP and a value is returned. So far, it
look like this:

<%@ Page Language="VB" %>
<%
response.ContentType="text/HTML"
dim strData
strData = Request.Form("invar")
Response.write (value calculated from "invar")
%>

While this seems small, I really need this to execute with as little overhead as
possible - right now, the first time I call any ASP.NET script on my server (even "Hello
World"), there is a 4 second long delay and I don't know why!

Can anyone tell me how I can get this script to execute with as little over overhead as
possible, and eliminate that 4 second delay???

The article
New Compilation Modes in ASP.NET 2.0
http://www.west-wind.com/WebLog/posts/2128.aspx
will provide some insight about what you're experiencing.

regards
A.G.

 

[Toni]

The article
New Compilation Modes in ASP.NET 2.0
http://www
will provide some insight about what you're experiencing.

regards

No, it didn't.

 

[Registered User]

No, it didn't.

Isn't the problem a 'slow' response when the page is initially called?
http://www.west-wind.com/WebLog/posts/2128.aspx
describes the default behavior

"In place compilation is ASP.NET 2.0’s default which compiles each
page in place when it’s accessed for the first time. This applies both
to Inline code (ie. Code and HTML markup in a single document) or for
ASPX + .cs/.vb source files specified with the CodeFile= attribute.
ASP.NET compiles both the ASPX and CodeFile when the page is first
accessed."

as well as an alternative to this default. Pros and cons of both
techniques are outlined. The document seems to answer the question why
(the response time is affected by the page being compiled in-place)
and offers an alternative (site pre-compilation).

regards
A.G.

 

[Toni]

Your document doesn't give me a direct solution. It DISCUSSES the issue, but doesn't
tell me how to modify my file, which is what I originally asked.

BTW, I'm on a shared server - I can't register a COM component, and I'm not trying to
compile anything.

 

[Registered User]

Your document doesn't give me a direct solution. It DISCUSSES the issue, but doesn't
tell me how to modify my file, which is what I originally asked.

BTW, I'm on a shared server - I can't register a COM component, and I'm not trying to
compile anything.

There is no modification to the file which will alter the default
behavior of in-place compilation. The alternative is to pre-compile
the site to alleviate the 'slow' first call issue. While it's not what
you wish to hear, these are your choices.

regards
A.G.

 

[Toni]

There is no modification to the file which will alter the default
behavior of in-place compilation. The alternative is to pre-compile
the site to alleviate the 'slow' first call issue. While it's not what
you wish to hear, these are your choices.

regards
A.G.

That's exactly what I wanted to hear. thanks.