Has there been any debate as to whether or not to store lookup table
information as application variables, or to use cached queries to retrieve
that information? Common sense would dictate that application scope
variables would use less space, but then you have to implement some shared
memory space management via CFLOCK.
I have an application.cfm file that loads some application level variables,
tests for the session, and loads some session/client level variables as
necessary... the thought being that accessing the variable directly instead
of querying for them would be more resource-savvy. I have over two dozen
lookup tables, and 40+ session variables. However, when I put the the
server under some moderate load [3 concurrent hits in the same session, via
frames], I can cause the app to freeze. I've set the server to single
threaded sessions, but that did not eliminate the freeze/lockup. What
gives?
It seems as though at times I'm getting a runaway thread [the # of running
requests in performance monitor is @ 1]. Unfortunately, I cannot reproduce
this behaviour on demand. What's the best way to track down the source of
the lock contention? I'm running CFAS 4.5.1 on NT4.
---
Daniel Dewey |"According to the rule of averages, if you
Unix/Internet SysAdmin | stand with one foot in a bucket of ice,
MCP (NT srvr/wkstn/eprise) | and the other in a bed of hot coals, you
| should be feeling fine" -- Unknown
The National Association of Colleges and Employers
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
