another alternative (and I'm only putting it forward as an alternative, cos I'm usually a publish to flat html kinda guy) is to add the queries into a shared scope (eg application) and then just read the application query as and when you need it, rather than doing another db hit.
Course, this is pointless with queries that change all the time, and you'd need to ensure that the app query doesn't timeout (with a schedule or something), but its something that I've used before (for an app that needed a lot of data from a very slow and complex query, but where you didn't want the user sitting there waiting for the query to return for ages - instead it ran every hour or so from a schedule and populated the app scope.) > -----Original Message----- > From: Damian Watson [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 10:54 > To: [EMAIL PROTECTED] > Subject: Re: [ cf-dev ] Performance > > > Yup about the caching... only 100 default. I seem to rememebr > a useful thing in caching is to cache a query for a long > period of time and when content is updated in your cfm to run > that query on the frontend so that the query basically only > ever operates when you make changes... is useful in some > instances anyway. > > ----- Original Message ----- > From: "Tomo Smith" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 22, 2003 10:46 AM > Subject: Re: [ cf-dev ] Performance > > > > I found using a mixture of SP and cached queries was the daddy, > > although Matt's idea certainly has promise, and is > something I've had > > a look at > > myself:) I also found that there's absolutely no point in > caching things > > that run very rarely as you wont get any gains from that. > It's also not a > > good plan to cache admin areas. > > > > Also remember that CF admin by default will only cache a certain > > number of queries (100 by default) - this can be changed through > > cfadmin though. If you're on a shared server, you'll be > sharing the > > cache with other sites. > > > > HTH > > > > Tom > > ----- Original Message ----- > > From: "Allan Cliff" <[EMAIL PROTECTED]> > > To: "CF - List" <[EMAIL PROTECTED]> > > Sent: Wednesday, October 22, 2003 10:32 AM > > Subject: [ cf-dev ] Performance > > > > > > Anyone like to share their opinion on improving coldfusion speed > > either by using stored procedures or caching queries? > > > > Which one is better? Or does it depend on the query. > > > > At the moment I have a mixture of them both with dynamic > queries as SP > > and basic queries q_GetCountries and q_GetStates as CachedWithin. > > > > Any comments? > > > > Thanks > > > > Allan > > > > > > -- > > ** Archive: > http://www.mail-archive.com/dev%> 40lists.cfdeveloper.co.uk/ > > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] For > > human help, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] For human help, e-mail: > [EMAIL PROTECTED] > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
