<< I'm a huge fan of the "build well, optimize later" approach to programming. Build your app as well as you can, using the simplest means reasonable, and be confident that the app is more than good enough until it's objectively demonstrated not to be. >>
Yep, that's the approach I take too. I'm constantly looking to improve application response once something new is up and running. One of the best ways of determining how something will act in a real environment is to let it run in that real environment and see how it does act, and then optimize from there. I suppose that's why query caching has always bothered me as far as optimization is concerned, because it really is a great bit of functionality but is largely unobservable in realtime testing. So many other aspects of the process are measurable, such as using cfstat, observing mysql query times, timing iterative processes, etc. Query caching is one of CF's few enigmas, particularly when it comes to its relatively unpredictable and unobservable use of memory. If you are using your own caching mechanisms or storing lots of data in application/session scopes in addition to query caching, you might as well throw a dart at a board to determine how much memory your CF cached queries are really using. Terry >If you really care that much, you're going to be doing some pretty >in-depth load testing anyway, so you can vary the different cache >amounts (query cache, other manual caches) and get app-specific >results. And even then, it's still irrelevant what the absolute >efficiency of the query cache is. It's a question of "good enough" >that can only be answered by testing your specific app. No >preexisting data will be meaningful, because your app will be >different than whatever app was used to generate the data. > >I'm a huge fan of the "build well, optimize later" approach to >programming. Build your app as well as you can, using the simplest >means reasonable, and be confident that the app is more than good >enough until it's objectively demonstrated not to be. So use the >query cache until it's been proven insufficient, and then find a more >efficient way to do it. But only worry about it if it's been >DEMONSTRATED insufficient. > >cheers, >barneyb > >On 12/7/05, Terry Ford <[EMAIL PROTECTED]> wrote: > >-- >Barney Boisvert >[EMAIL PROTECTED] >360.319.6145 >http://www.barneyb.com/ > >Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:226523 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
