You probably answer the performance issue by yourself when you said “that you use FindPagesWithCritera a lot”, don’t do this or cache the result (as you say) I have written a minimal blog entry how to use the EPiServers cache functionality in EPiServer version 5 and later
Here are some guidelines for FindPagesWithCriteria:
http://labs.episerver.com/en/Blogs/Steve-Celius/Dates/2009/8/FindPagesWithCriteria-and-Performance/
Great article Steve, it probably should be in the SDK!
But how is your FindPageswithCriteria for your XML page provider written(is it going throw every XML file and looking for properties – it can be extremely heavy)?
I've implemented the XML Page Provider and it's been working pretty good for a few months now. We've decided to have a solution where every page has it's own folder, containing the XML declation and associated files for download.
Shortly the number of pages/xml-files will increase from 100 to several thousand, so I've started to do some performance testing. Unfortunately once I've added more than 500 XML files the performance as dramatically low, and the site hardly loads at all.
I've read the article on http://world.episerver.com/Blogs/Ben-Morris/Dates/2009/10/Developing-EPiServer-page-providers-optimizing-performance/.
We are using the FindPagesWithCriteria() quite a lot, so can anyone help us with caching and general performance increase?
Regards
Jakob