Question on storing queries in session arrays
in [Advanced Techniques]
|
Prev: can you not set a variable that's in the same scope as a query structure
Next: Retaining Ms Word formatting in text field capture
From: CFMXPrGrmR on 22 Apr 2008 12:21 I'm curious how much memory storing queries in session arrays take up. The query results themselves (about 5-6) are small, not more than 100 records. The site traffic is low, not more than 100k a month but is expected to jump to over 1 million. The web server (primary and failover) are beefy systems, I believe 4gigs of ram. So I don't imagine I should be concerned?
From: Ian Skinner on 22 Apr 2008 12:38 CFMXPrGrmR wrote: > I'm curious how much memory storing queries in session arrays take up. The > query results themselves (about 5-6) are small, not more than 100 records. The > site traffic is low, not more than 100k a month but is expected to jump to over > 1 million. The web server (primary and failover) are beefy systems, I believe > 4gigs of ram. So I don't imagine I should be concerned? > Ultimate a record set [i.e. query] is just an array of structures and as such should have only a small bit of overhead above and beyond the data in the query. Now what is in each query can very greatly. If that is five or six, one hundred record queries with each storing large CLOB or BLOB fields that could easily be many megabytes of data. But in most normal situations, no you should not have a problem. But only performance testing will say for sure.
From: CFMXPrGrmR on 22 Apr 2008 13:17 Thanks Ian. No, they are simple text results that I want to carry throughout the whole site. Currently we're just querying on each page where we need the results. It's somewhat painful.
From: Ian Skinner on 22 Apr 2008 13:22 CFMXPrGrmR wrote: > Thanks Ian. No, they are simple text results that I want to carry throughout the whole site. Currently we're just querying on each page where we need the results. It's somewhat painful. You will also want to make sure these are unique results for each user. If the results are not unique per user, but are same for all users throughout the site, then you probably want to use application scope, or possible server scope. Then you only have one instance of the query used by all sessions rather then one million copies of the same query.
From: CFMXPrGrmR on 22 Apr 2008 15:00
They aren't specific to the site users, just the site itself. These results are usually returned once each morning, so I would probably cache the query/array values. Are there any issues caching values in the application scope? |