> Personally I've tended to store my global settings in an
application-scoped struct, but duplicate them into request scope for
unlocked usage


I arrived at this solution a long time ago when we were using CF4.5 and had
locks throughout our code. Performance was totally dead by 200 users and
locks were timing out all over the place. By altering the application to
duplicate into the request scope we eradicated the need for about 98% of the
locks in our code and the performance limits under load testing went up from
200 to over 3000 simultaneous users. In production, we never got anywhere
near 3000 simultaneous users and the systems we were serving about 3 million
pages a month. We continued this practice in CF5 as it seems that it
suffered with the same problems.


Since moving to CFMX 6.1 I have become more relaxed about using cflock
throughout the applications we write as the entire model just seems to be so
much quicker and more reliable.


Paul
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to