Probably discussed to death 10 years ago, 5 years ago, one day ago. I
don't know. Can't find definitive answers.
Wondering...
Does anyone think or dare I ask does anyone know if one type of
variable structure is faster or less resource intensive than another?
In particular, I have an app
I'd look at what you need to solve here: do you really need client vars or
session vars?
performance wise, session vars would be faster as they are in RAM where you
have your client vars set to use a DB. A DB lookup is going to be slower
than RAM.
DK
On Tue, May 27, 2008 at 9:05 AM, Derrick
From my experience anything will be faster than a cookie.
mf
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas
Knudsen
Sent: Tuesday, May 27, 2008 9:57 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Speed and resources: better to do
It is a balancing act. For sites without too many visitors I prefer session
vars for security and speed. Too many is a function of how much memory
the server has and if there are multiple sites running on it etc. Modern
hardware usually has so much memory that you can easily track thousands of
Also remember the more you have to add stuff to a cookie the longer the
request is going to run because the cookie is submitted on every request. So
right now it might be just a couple of variables but, as
scope inevitably creeps so will the time of every request.
On Tue, May 27, 2008 at 10:18
Session variables are faster generally and solve all the issues you need.
There are always trade offs. For example saving the info in a session scope
with take up the server's memory as oppose to saving the info in a client
variable cookie, etc. But in most cases, approx. 98% of the time, the
I second that.
I think however, and there is a big I think there that technically the
request scope is the fastest but of course it doesn't maintain state so
probably not what you want. If the variables don't change values then you
could consider the application scope.
-d
_
From:
