We just switched away from client variables, and now use only session variables. We got an enormous increase in performance. The database guys were complaining about the performance impace from all the reads -- let alone the writes -- due to storing variables in the database.
Recall that CFMX (like CF before it) reads all the user's client variables at the beginning of any HTTP Request that uses even one client variable. All the user's client variables are then written back to the database at the end of that HTTP Request. We definitely experienced some issues with scaling. (CFMX for J2EE, WebSphere, Oracle 10g, 3,000 to 4,000 concurrent users, database-intensive application) Chris Norloff ---------- Original Message ---------------------------------- From: <[EMAIL PROTECTED]> ... >But as a test, I tried switching to client variables (using database) >and we took a serious performance hit (probably 50%) with the current >application. I'll do my best to streamline it during the rewrite, but >does anyone have any suggestions on the best route to take here? > >Thanks, >Jonathan ... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:189007 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
