>Unless client variables are stored in the registry as an automatic >part of using clientmanagment, I don't have any there. I've never >used any cookies or stored client info in the registry. There's also >still 5 GB of space left on the drive, so I don't think hard drive space >is an issue, unless the registry is set to a limit on how much it can use, >but even so, these are low-traffic sites, with few users that log in to >performance management functions.
Two things. First, yes, the registy is the default setting in the CF Administrator to store client variables (a "feature" I've always disagreed with). If you're using the registry, I think your first step should be to change this setting to use a datasource and use your DB to store client variables. Then go back and delete the client variables from yoru registry to compact it a bit. Using your registry, CF-wise at least, for anything other than system settings is a risky practice. Second, there is a registry limit size, and it's not the amount of space left on your hard drive (thank God!). If you go to Control Panel-> System -> Advanced -> Performance Options -> Change... (under Virtual Memory), you will see a size limit that you can edit for your registry. It will also show you the current registry size. You should be able to then answer the question as to whether or not your registry is full or close to full. >I do have issues with memory leak due to several websites running >that don't have the session and application variables locked properly. >(They were built before I knew better and haven't had time to rewrite them) >But I've been running these sites for a couple of years without problem, >except for the memory loss, which causes me to have to reboot the >server about once a week, so it hasn't been a big deal. While I don't know if the two problems are related, I would highly suggest finding the time to go back and lock your shared-scope variables. We're still using 4.5.2 ourselves at my company, and when I first started here, our site was constantly crashing. I spent my first two weeks doing nothing except locking shared scope variables, and we haven't crashed since. I think versions of CF prior to 5 did a particularly poor job of shared memory management, and isn't something that should be overlooked. Regards, Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
