Ken
Tue Dec 16 19:00:56 CST 2003
Hi,
a) Variables only need to be declared if Option Explicit is on.
b) A variable will be initialised
c) In theory, yes
d) No
Usually, when looking at ASP applications that exhibit poor performance that
occurs over time (i.e. scalability problems as opposed to code that always
has run slowly) I typically see things like:
a) heavy use of looping in recordsets to find matching records, rather than
using an inline SQL statement or stored procedure to return only the
matching record(s) required
b) use of/creation of recordsets inside a loop (rather than using a JOIN, or
similar to return just the one recordset)
c) use of heavy cursor objects (adOpenStatic) rather than lightweight
cursors (adOpenFowardOnly/adLockReadOnly) - place records into VBScript
variables using .GetRows and .GetString() then dispose of the recordset and
connection
d) incorrect use of connection pooling. Rather than explicitly creating and
disposing of connection objects, connection objects are implicitly created
(by passing a connection string to the .Open method of the recordset or
command object. This causes another connection to be created):
http://support.microsoft.com/?id=191572
Cheers
Ken
"moron101" <moron_rsoh@yahoo.com> wrote in message
news:3CE090C8-4304-42DB-B9D0-295B9CFC93C1@microsoft.com...
: Hi Everyone,
:
: I wrote my first "prime time" web application in ASP and IISv5 from start
to finish designed to handle gobs of transaction to MS-SQL v7 but I'm
finding that my performance is slowing after weeks of external load testing.
In the beginning my website was lighting quick, now only fast. I suspect
poor programming practise as the culprit thus the questions:
: 1) Must all variables be declared before use?
: 2) What are the ramifications if not declared before use?
: 3) Is there a "garbage collector" similar to Java?
: 4) Is there a way to recycle the IIS instance without killing the
"Application object" within ASP?
:
: Many thanx in advance.
:
: Regards,
: Richard
: