Client Variables

hi list . . . I have newly become acquainted with Client Variable storage issues and now have them being stored in a datasource . . . Problem: Using the zip file templates from MacroMedia website for deleting client variables from the registry, it is cludgy, time consuming, slow and burns up the CPU . . .(reminds me of CFMAIL) Question .  ..? Can I simply go into the area of the registry where the client variables are stored and simply manually delete them without fear of total server meltdown?? any help to quickly remove THOUSANDS of client variables from the Windows2000 AdvancedServer registry would be most welcome!

I wouldn't mess around with manually deleting client vars. You can let CF do it with a bit of help.  set client var timeouts to, say, 1 day for awhile.  Long enough for the CF Executive (or whatever passes for it in MX) to completely clean out the registry.   It may eat a fair amount of CPU time on that first hop from 90 days to 1.  If you want to nursemaid the thing, set it to 60 days, then tomorrow set it to 45 days, then the day after set it to 30 and so on.  Or just go to 1 day and consider it penance for letting CF go to the Registry in the first place :D -------------------------------------------- Matt Robertson       matt@mysecretbase.com MSB Designs, Inc.  http://mysecretbase.com -------------------------------------------- hi list . . . I have newly become acquainted with Client Variable storage issues and now have them being stored in a datasource . . . Problem: Using the zip file templates from MacroMedia website for deleting client variables from the registry, it is cludgy, time consuming, slow and burns up the CPU . . .(reminds me of CFMAIL) Question .  ..? Can I simply go into the area of the registry where the client variables are stored and simply manually delete them without fear of total server meltdown?? any help to quickly remove THOUSANDS of client variables from the Windows2000 AdvancedServer registry would be most welcome!

OK, first GET YOUR CLIENT VARIABLES OUT OF THE REGISTRY!!! Sorry to be so "Shouty" about it, but it'll eventually kill the server! Make a datasource and link the client storage to it Then worry about your registry later, but do not leave your client storage to Registry ----- Excess quoted text cut - see Original Post for more -----

I think he did already: "now have them being stored in a datasource . " Now he's worried about what is left over in the registry. ----- Excess quoted text cut - see Original Post for more -----

> I think he did already: > > "now have them being stored in a datasource . " > > Now he's worried about what is left over in the registry. Ah, I jumped on it as soon as he said he had them in the registry... My over-reaction, sorry <g>

yup .  . . so now, is it OK to manually remove them or SOME of them anyway . . .there are over 320,000 in there now and it IS affecting performance . . . so while they are now being stored in a datasource in another server, i still would like to remove a hefty amount of them manually if it is safe that way . . . I changed the expirey to 1 day from the default 10 . . . but I dont know if that will cause EXISTING client variables to expire with the new setting or existing ones still hang out for 10 days . . what do ya'll think?? jim PS .. .yes, i deserve to be flogged . . ;-') At 09:44 PM 4/15/2003 +0100, you wrote: ----- Excess quoted text cut - see Original Post for more -----

Changing the inactivity period to 1 day will cause client vars *resident in the registry* to expire after 1 day of inactivity.  Since all *new* cvars are now being stored in a datasource, that means all registry cvars will meet this inactivity criterion after 24 hours and be deleted. As for whether its safe to burrow into the Registry for any reason... as I said before if it were me I wouldn't go there unless held down and forced.  Just me being a big chicken :-) ------------------------------------------- Matt Robertson,     matt@mysecretbase.com MSB Designs, Inc. http://mysecretbase.com ------------------------------------------- Reply-To: cf-talk@houseoffusion.com date: Tue, 15 Apr 2003 19:14:09 -0400 ----- Excess quoted text cut - see Original Post for more -----

Setting the purge interval to a lower value will cause them to be purged sooner. If this is CF5 though, be aware that you need to manually change the value in the registry: http://www.macromedia.com/support/coldfusion/ts/documents/tn18128.htm. And, if you want them to purge immediately rather than waiting for the next purge cycle, restart the CF Executive service and it will begin 30 seconds later: http://www.macromedia.com/support/coldfusion/ts/documents/client_var_purge.htm You can also manually remove the individual client variables from the registry. Deb yup .  . . so now, is it OK to manually remove them or SOME of them anyway . . .there are over 320,000 in there now and it IS affecting performance . . . so while they are now being stored in a datasource in another server, i still would like to remove a hefty amount of them manually if it is safe that way . . . I changed the expirey to 1 day from the default 10 . . . but I dont know if that will cause EXISTING client variables to expire with the new setting or existing ones still hang out for 10 days . . what do ya'll think?? jim PS .. .yes, i deserve to be flogged . . ;-') At 09:44 PM 4/15/2003 +0100, you wrote: ----- Excess quoted text cut - see Original Post for more -----

hi list . . . I have newly become acquainted with Client Variable storage issues and now have them being stored in a datasource . . . Problem: Using the zip file templates from MacroMedia website for deleting client variables from the registry, it is cludgy, time consuming, slow and burns up the CPU . . .(reminds me of CFMAIL) Question .  ..? Can I simply go into the area of the registry where the client variables are stored and simply manually delete them without fear of total server meltdown?? any help to quickly remove THOUSANDS of client variables from the Windows2000 AdvancedServer registry would be most welcome!

I'm catching up on messages and this may have been said already but it is very important to move client variable storage over to a database from the registry.  Once this is done cleaning up the entries from the registry should be safe if someone has comfort in working in the registry. Kind Regards - Mike Brunt Webapper Services LLC Web Site http://www.webapper.com Blog http://www.webapper.net Webapper <Web Application Specialists> [mailto:Rodney.Bruce@HQISEC.ARMY.MIL] Sent: Friday, April 18, 2003 8:33 AM To: CF-Talk Subject: RE: Client Variables hi list . . . I have newly become acquainted with Client Variable storage issues and now have them being stored in a datasource . . . Problem: Using the zip file templates from MacroMedia website for deleting client variables from the registry, it is cludgy, time consuming, slow and burns up the CPU . . .(reminds me of CFMAIL) Question .  ..? Can I simply go into the area of the registry where the client variables are stored and simply manually delete them without fear of total server meltdown?? any help to quickly remove THOUSANDS of client variables from the Windows2000 AdvancedServer registry would be most welcome!

One step you might take in CF Administrator is to set client variable storage to one (1) day.  I don't think it will allow less than that.  Even though you are storing variables in a database, CF still adds a bunch of stuff in the registry on a seemingly constant basis.  This will force CF to purge client variables older than one day from the registry in the background.  (At least in CF 5.0) Second, and I am not sure if this would help, but that would be to disable the CFRegistry tag. Third, review your variables in CFAdministrator, and make sure none on the list are routed to the registry.  These are set by default by the CF installer package. Monitor the Server logs, and you will see that it will still be purging registry entries in the background constantly. One feature request that has been submitted to MM is to shorten variable storage to less than one day. Another is to have a function to purge the MRU streams as well, as these combined contribute greatly to registry bloat.  If you are very comfortable with working with the registry, a workaround is to run on a scheduled basis, a regsrvr command that will clean out these entries several times a day.  Use this workaround with extreme caution to avoid corrupting your server registry.  Also schedule Regclean.exe to run at least once every 24 hours. Also be sure to set your registry size limit to at least twice the existing size, which will help prevent server crashes. Your mileage may vary..... ====================================== Got DSL?  New low prices! Check it out! For hosting solutions http://www.clickdoug.com ISP rated: http://www.forta.com/cf/isp/isp.cfm?isp_id=772 ====================================== If you are not satisfied with my service, my job isn't done! | I'm catching up on messages and this may have been said already but it is | very important to move client variable storage over to a database from the | registry.  Once this is done cleaning up the entries from the registry | should be safe if someone has comfort in working in the registry. | | Kind Regards - Mike Brunt | Webapper Services LLC | Web Site http://www.webapper.com | Blog http://www.webapper.net | | Webapper <Web Application Specialists> | | -----Original Message----- | From: Bruce, Rodney S HQISEC/Veridian IT Services | [mailto:Rodney.Bruce@HQISEC.ARMY.MIL] | Sent: Friday, April 18, 2003 8:33 AM | To: CF-Talk | Subject: RE: Client Variables | | -----Original Message----- | | Sent: Tuesday, April 15, 2003 10:54 AM | To: CF-Talk | Subject: Client Variables | | | hi list . . . | | I have newly become acquainted with Client Variable storage issues and now | have them being stored in a datasource . . . | | Problem: | Using the zip file templates from MacroMedia website for deleting client | variables from the registry, it is cludgy, time consuming, slow and burns | up the CPU . . .(reminds me of CFMAIL) | | Question .  ..? | | Can I simply go into the area of the registry where the client variables | are stored and simply manually delete them | without fear of total server meltdown?? | | any help to quickly remove THOUSANDS of client variables from the | Windows2000 AdvancedServer registry would be most welcome! | | | | |