Thread

After look at all the tips on optimizing an EE site, I asked the host to check if they are running query caching. They said they were and gave me the settings which were:

query_cache_limit=2M
query_cache_size=8M
query_cache_type=1

Now from what I’ve gathered our size should be a lot higher (I had them change the query_cache_size to 128M, but I have no idea what the query_cache_limit should be. The main edit page seems to time out now after I turned off EE’s query caching so I was wondering of you had any recommendations.

This is an EE1.6.8 MSM site with approximately 30K+ entries, 3 sites and averages 1000 visits/hr during a weekday.

Thanks.

Hi Kyle,

I’m afraid that this is a question that is we can’t really answer since it is dependent upon your own server environment and your particular installation. Your host would be best placed to provide guidance for you since they have access to the necessary monitoring tools. Solspace provide an evaluation service that might well encompass these issues but as I say, in the first instance your host should be best placed to advise you.

Cheers

Greg

Hi Kyle,

I’m afraid that this is a question that is we can’t really answer since it is dependent upon your own server environment and your particular installation. Your host would be best placed to provide guidance for you since they have access to the necessary monitoring tools. Solspace provide an evaluation service that might well encompass these issues but as I say, in the first instance your host should be best placed to advise you.

Cheers

Greg

Maybe a ballpark idea, a range, a minimum you could suggest? I don’t think we should have to shell out $3,500 just to get a recommendation for a setting. I’m not asking for an exact number, just some guidlines.

The main reason I’m asking is that since I turned EE caching off we’re getting blank white pages in the CP when accessing large Edit pages and other assorted CP pages where we weren’t having this problem before.

Hi Kyle,

Let me ask the rest of the team whether there is any general guidance we can offer. With regard to the blank pages in the CP, you have turned off EE’s DB caching?

Cheers

Greg

Hi Kyle,

Let me ask the rest of the team whether there is any general guidance we can offer. With regard to the blank pages in the CP, you have turned off EE’s DB caching?

Cheers

Greg

I’ve set “Enable SQL Query Caching” to “No”. Thanks.

Kyle,

What was the impetus for making these changes? EE’s query caching setting shouldn’t affect the control panel; only the front-end. I suspect the MySQL cache changes are the culprit here.

What was the impetus for making these changes?

Every article about optimizing an EE site says if the host is running SQL query caching to disable EE’s query caching. I asked the host (we’re on a VPS), they said they were running Query caching, so I disabled it.

As far as the blank pages, after spending a number of days with it, I think the cause was specific to FF4 and and Avast! Antivirus Web Shield. Safari didn’t seem to have the same issues and the client never reported a problem. I just disabled it and FF4 seems OK now, but back to the query_cache_limit question…

Maybe a ballpark idea, a range, a minimum you could suggest? I’m not asking for an exact number, just some guidelines.

Kyle,

Its actual more complicated than that. The actual size of this cache and number of query result sets cached is dependent on the amount of memory available to your MySQL database server.

Good article here and here

The values you have seem perfectly reasonable. To measure it though or to see the benefit you will need to use something like MySqlTuner or similar.

Some more info available here in PDF form

O