Mark, I didn't go into further depth because I was not interested in the sessions side of things, except when I start implementing the method I wanted to know a way of comparing whether what I am trying to do achieve reduces the amount of memory used.
We have applications that are chewing through too much memory, and I need to reduce this quickly and find a solution that will work. Here is the problem I have 80 users on this system, and every time they log in and logout they are creating another session, multiply the number of users by 500k by 100 logins an it starts adding up. My solution is to start reducing things that don't need to be held in memory, but I would like to know how much memory certain variables are taking up if this is at all possible. I don't like using session either, as it is very non cluster aware unless using sticky sessions. But that defeats the purpose of off loading in a cluster in my eyes. But that is another story. All I am asking, is there a way to see how much memory a variable is taking up. And I am already aware of the SessionEnd and SessionStart of CF7.0, but its not what I am asking. Regards Andrew Scott Technical Consultant NuSphere Pty Ltd Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9686 0485 - Fax: 03 9699 7976 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stanton Sent: Tuesday, 1 March 2005 12:40 PM To: CFAussie Mailing List Subject: [cfaussie] Re: CFCs calling CFCs Hey Andrew > What I mean by this is that when a session ID is changed the memory > still holds the session variables until expiry, I know I could perhaps > go and do a kill on these unused session vars. How do you know that a session variable is unused unless it has expired without reading a user's mind? By definition session variables should be considered in use until they expire, at at that point CF marks them as ready for garbage collection so I wouldn't spend time worrying about this too much. The best way to keep memory to a minimum would be to persist the more complex/large data structures and just store a key in memory so you can easly fetch them out when you need them. However you would then need your own garbage collection system to clean out these records from the DB. In general I don't like the idea of stuffing lots of stuff into the session scope. I get especially fustrated when I see multi-step form processes relying on session scope to store the data from the preceeding steps. On another note (and I'm not trying to flame, or start another upgrade/don't upgrade war) its worth noting that CF7 introduces the idea of onSessionEnd(), which would allow you to clean any values that have been persisted temporarily as soon as the session expires. Cheers Mark -- Mark Stanton Gruden Pty Ltd http://www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
