Purple Turnip

maybe but i've never in my entire programming life had a page that runs 75 db queries (cept for db updating scripts/cronjobs, but speaking pages accesible by webserver). The thought of having that many just gives me chills and would keep me up at night.

to put that into context if you website had about 100 users online all running 75 queries each = 7500, i think for any webserver thats quite a few. Might not bring it down but enough to make you worry. (oh ipb has summit like 600 online atm).

I'd prefer if it was on DEMAND so that IPB can decide which queries are better for SQL caching and which ones aren't.

This sounds like a fairly useful thing that can really help out with the server load.

You can just sign out, and click Register. Simple.

The mySQL query cache has three states: OFF, ON, ON DEMAND

m4rtin, only if it is set to "ON" will it cache all queries. Mine is set to "on demand" which means you have to tell it which queries to cache.

It would be a bad idea to cache all the queries on IPB anyways.

I'm installing DEMAND based sql_query_cache and I want to know if IPB will take advantage of this automatically?

i have heard that ms-sql runs faster than mysql. of course it depends on how the application and configuration. but does somebody have experience running ipb