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
