Thread

I suspect this is possibly a network issue but want to check to ensure it’s not a bug.

I upgraded to 1.6.3 from 1.6.2 after my site slowed to a complete halt due to large amounts of concurrent MySQL connections. I optimised and terminated every unneeded call and followed the suggestions found here: Reduce Queries Docs and here: Optimise EE Docs.

Enabling caching for all templates was the one thing that resolved the issue and site performance increased dramatically. The cache problem arose several hours later when only a partial page was returned, it seems that the cache writing process wasn’t completed or was interrupted so some (but not all) images, imported scripts etc were missing. Clearing the cache and recalling the page fixed it.

Has anyone encountered this behaviour? Any suggestions to prevent it from occurring? I guess increasing the cache index interval to days or weeks would lessen the risk of serving incomplete pages but not an ideal solution, is there a maximum cache period?

Best wishes,
Jay

Update: the same thing has happened again. Templates are set to be cached after 60 mins but after 3 cycles there are images missing again. Server load/traffic is currently low.

Well, even upping the cache time, the cache will fill up and may ‘bump’ items out.  So agreed- not a great solution.  I’d take a hard look at the templates- turn cache off, see how many queries are actually being generated w/out caching- and how complex those queries are.  If there are a lot?  Might be worth taking another look at your templates again.

As to what’s up at the moment, I’d almost suspect something ‘off’ in caching.  But it did clear properly when you cleared them manually via ‘Admin- Utilities’?  That suggests all is well.

With the missing images and such- if you view the rendered code, are the image links in there- just 404’ing, or is the page stalling and the html incomplete?  Also- what kind of imported scripts are we talking about?

Sorry, my mistake/oversight: forgotten that I had browser detection running. When the cache page was created with a user running IE6 I was viewing the wrong css and js etc

No cache bug! Thanks for your help and apologies for wasting your time.

Jay

Hm- I wouldn’t have thought of that one, so glad you let us know what was up.  And glad it was not a bug 😉.

Closing this one out.