Ralf, There are a couple of other things to try: a) Put the files in /dev/shm (assuming you have enough memory). Since it's located in memory which is a lot faster than disk this will reduce your delete time b) When you need to delete all cache simply rename the old directory and re-create the original one and then delete the new-renamed direcotory. This isa hack but if everything else fails this will solve....
On Mon, Apr 21, 2008 at 3:40 PM, Ralf Eggert <[EMAIL PROTECTED]> wrote: > Hi Fabien, > > > In your specific case, the sqlite backend sounds better (because it > > will use an index for the clean method). > > This sounds good. I will give it a try tomorrow and report here if it > improves the performance. > > > Sometimes, it's not a good idea to cache too many things. Maybe you > > would have better results with caching only HTML final results than > > intermediate database calls. > > I actually do HTML template caching as well. But these database selects > are used on more than one page or the data doesn't change that much but > I do want the HTML page to be rendered more often. Some selects are even > used in hundreds of pages, so caching these results will improve a lot > of pages. While depending only on HTML template caching will need all > these pages to do the same database select. > > Thanks and best regards, > > Ralf >
