>- see footer for list info -<
Thanks for all those comments, Tim. I have come to the reluctant 
conclusion that it is not going to be a viable option on this 
application. Apart from the fact that there is not one line of OO in 
this app, I now realise that you can't (easily) drop all cached queries 
related to a table/namespace/whatever as there is no real way to get at 
the list of stored keys.

Works fine in MySQL ! and I think that is where we may have to leave it, 
though a few more queries cached via CF may be possible.

The site is very data-intensive (www.football.mitoo.co.uk). If as you 
say the cost of serialise/deserialise is high, whilst using it might cut 
down on traffic to the MySQL server, performance may suffer.

Thanks anyway! (Of course, I may return later.......)
Cheers
Terry
(free event listings at http://www.confexdb.co.uk)

----- Original Message -----

> *From:* Tim Blair <[email protected]>
> *To:* ColdFusion Development <[email protected]>
> *Date:* Mon, 12 Oct 2009 11:49:42 +0100
> 
> >- see footer for list info -<
> Terry,
> 
> > At least, if I understand it right, with memcached we could cache a
> > query (each one having an individual key) and if a related table is
> > changed with an SQL update/delete/insert in our code, we can 
> > designate
> > an immediate dropping of the named/related cached query. That way 
> > it is
> > ready to be recreated the next time it is called for.
> 
> Ah, that reminds me of a quote by Phil Karson[1]:
> 
>     "There are only two hard things in Computer Science: cache
>      invalidation and naming things."
> 
> We use memcached with CF8 heavily on White Label Dating[2] to cache
> both data structures (e.g. complete member profiles) and pre-rendered
> HTML pages (and sections of pages).
> 
> We don't use it directly for storing CF query data because the
> serialisation/deserialisation is very heavy for those objects, and we
> find it's much more efficient just to store the data we actually need
> without any extra columns, query metadata etc.
> 
> We use a customised version of Shayne Sweeney's CF client[3] as a base
> with a couple of façade components sitting on top to provide custom
> handling of things like initialising the client, setting cache
> timeouts, using counters, batching requests together nicely etc.
> 
> If you've got any specific questions about implementing memcached,
> fire them over and I'll see what I can do to help.
> 
> Tim.
> http://tim.bla.ir/
> 
> [1] US programmer from Xerox/DEC/Netscape:
>     http://www.nndb.com/people/400/000031307/
> [2] http://www.whitelabeldating.com/
> [3] http://memcached.riaforge.org/
> 
> _______________________________________________
> 
> For details on ALL mailing lists and for joining or leaving lists, go 
> to http://list.cfdeveloper.co.uk/mailman/listinfo
> 
> --
> CFDeveloper Sponsors:-
> >- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -<
> >- Lists hosted by www.Gradwell.com -<
> >- CFdeveloper is run by Russ Michaels, feel free to volunteer your 
> help -<
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.421 / Virus Database: 270.14.10/2429 - Release Date: 
> 10/11/09 18:34:00
> 

_______________________________________________

For details on ALL mailing lists and for joining or leaving lists, go to 
http://list.cfdeveloper.co.uk/mailman/listinfo

--
CFDeveloper Sponsors:-
>- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -<
>- Lists hosted by www.Gradwell.com -<
>- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<

Reply via email to