Hi, I've never read anything about this so this q is for the gurus!  Please
read completely and thanks for your attention.  Let me describe the issue
then I'll ask my question.

I've pretty much stuck to client vars to avoid ugly locking code.  However
now, I have a use for them.  I need to store dozens of queries in a
structure in the session scope.  I've got it coded and it works like a
charm(Yes its locked) saving lots of time for the database server.  The
performance savings is dramatic as the queries that were repeatedly
generated each time took time away from other tasks.  Client vars might not
be so good as I"d have to wddx the whole thing back and forth which would be
a big chunk of data to and fro from the server.  Plus the serialization and
deserialization overhead.  Cacheing the queries is not good as each user
will have different queries.

So, to my question.  I've estimated this would take a gig of ram per server
to store these queries for all of our users.  So, (1)is there a way to
measure how much memory is being allocated for session vars?  (2)When I look
at the cf memory, will it go from 60megs to a gig?  Anyone tried this and
gotten burnt?  Thanks.  DRE

______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to