the basic fact is that there is an awful lot going on and the more people ask for…. well speaks for itself.

I am continually looking at ways to optimise and it is, to me, a priority whenever there is time of work needs to be done. However it must be realised that a forum is not like a blog - it is a far more dynamic venture even down to behaving and displaying differently depending on who the viewer is.

No it will not work with wp-supercache.

I have no idea why there should be 15 extra queries on a blog page but I will see if I can pin that down. An awful lot of effort has gone in to ensuring that components are NOT loaded if not needed. Sadly, while WP hooks (actions/filters) are an extremely useful coding tool to enable authors to change and modify behaviour, they rarely pass enough data along to make useful judgements and one quite often has to perform a db read to get te data needed. But 15 sounds far too high.

It's tempting to say that for a stipped down version just go back to version 1, 1.1, 1.2 etc…! That will work!

Having said that I have spent much of the last two weeks stripping the code down and rebuilding with a new query model - especially hitting the areas that get used the most and/or put the most strain on the DB. The good news is that the version I am testing now (a sort of pre-alpha 3.1!) has, on average, reduced the number of queries by about 75% and in some cases more. This is, of course, a huge improvement but it is going to require some solid testing before I can release it. So we reckon about 3-4 weeks.

I don't like putting releases out quite so often but in this case it will be worth it as the benefits are obvious. And all of that without losing any functionality….