why don't you just 'set' the cache when the update to the content item occurs?
for a news-site this would be ok, as you hardly 'retouch' any published articles which are old, and you would avoid the initial hit on the story that way as well. regards Ian On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > What about smarter cache system? I mean update not only by time-out, > but also by a DB change. > > In a news sites it will be especially usefull: content can update not > only each 'xxx' minutes, but it can also update by content > addition/edit/deletion. > > I suppose, that such system can be built in any Web system and > especially in Django. I also know that such a cache will give really > good perfomance improvement, since I realised it (using PHP) on two > sites, and one of them was quite popular news site. > > The idea is quite simple: track DB updates and time. One of the event > will occur faster and will cause to update the cache (or mark it > 'dirty' in my terminology). So, anyway, we will have site always up to > date, we will have no outdated pages (with "Today is: Tuesday, > November, 2005", when it is 2006 year already) and we will lower > regenaration frequency. > > If you will find these idea interesting, I can publish PHP > implementation and give needed comments and explanation. I just learn > Python, so I can not port it on my own right now, but I can provide > full design, so, I suppose, it can be ported and integrated easily. > > Regards, > /Alexander. > > -- [EMAIL PROTECTED] -- blog: http://feh.holsman.net/ -- PH: ++61-3-9877-0909 If everything seems under control, you're not going fast enough. - Mario Andretti
