Well if you are running SQL and CF on the same server, ESPECIALLY do not use
session variables, because SQL is a friggin RAM PIG that needs the biggest
trough and most amount of slop you can afford. In a production enviroment
SQL should be on its own box. If SQL is on its own box, any network traffic
will make the client variables slower. Again slower counted in milliseconds
which is still not enough reason to use session variables.
----- Original Message -----
From: "Nat Papovich" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Monday, February 26, 2001 12:47 PM
Subject: RE: cflocation, addtoken = yes||no
> I'm going to HAVE to chime in here and muddy the waters for ya -
>
> Client variables have been measurably faster than session variables in
tests
> I have run, using CF4.01 and SQL Server on the same machine.
>
> Now that that's a fully qualified statement, I'll let you make your own
> decisions, and run your own tests.
>
> NAT - Allaire Certified ColdFusion Developer
>
> > > Secondly how does it impact performance having to constantly update
and
> > query a
> > > database.
> >
> > Yes, session variables are faster because you do not have to hit the
> > database to get at them, however the speed difference is
> > milliseconds which
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
