High query count

[allen]

See Nick Dunn's very thorough email on 17 June titled "S3 performance and still high use of SQL queries"—here is an excerpt:

When using filters. these are compiled into a single query that's executed before the above "content" queries are run. It would actually be possible to concatenate ALL queries into a single SELECT, thereby reducing a "sections" Data Source to one query only. And if that one query executes in ~1ms that's a massive win.

One of the biggest worries people have had with S2 was the high query count associated with heavily normalised content, so I do hope it's not too late in the day to put some thought into reviewing this. I tried with S2, but it was too big a job to refactor with an established code base. With S3 still in a state of flux I think there is room for improvement after a little lateral thinking.

(It has been suggested before e.g. the first comment on this post http://symphony-cms.com/discuss/blog/entry/squeezing-more-juice-from-symphony-queries/, and again here http://symphony-cms.com/discuss/thread/44556/)

[allen]

From Alistair:

I agree this needs to be looked at, however it is a big job. Needs some pen & paper conceptual discussion I think.