modx - slow pages loading for large site

Are you caching all the Ditto calls or not? Unless you are, I would not expect it to perform very well with that many documents. Perhaps you need a custom snippet to summarize that many documents, but you at least need to make sure you are caching the Ditto calls; you simply need to refresh the site cache when publishing new articles in the Ditto directories. You can do the same with Wayfinder, as well, since we are talking about an immense amount of data being transfered over the pipe on each request that dynamically looks for documents.

All Ditto calls are cached. I have also made sure that Wayfinder calls in the templates are now [[cacheable]]. Though I assume that Wayfinder will not have much bearing on this issue as none of the Ditto items are set to display in the menu?

Quote from: OpenGeek at Sep 25, 2007, 11:48 AM

Perhaps you need a custom snippet to summarize that many documents

How do you envision that working?

Thanks for your help.

Hi,

i have no fix to solve your issue but your pages are really heavy
your homepage weight is 272 KB (287 KB uncompressed)


:-)

Also, your webserver error logs should have more details on any PHP errors that might be causing the 500 Internal Server error.

i have no fix to solve your issue but your pages are really heavy
your homepage weight is 272 KB (287 KB uncompressed)

Yep the homepage is probably the largest page with all that imagery. Most other pages should be anywhere near that.

Quote from: OpenGeek at Sep 25, 2007, 12:45 PM

Also, your webserver error logs should have more details on any PHP errors that might be causing the 500 Internal Server error.

I’ve requested the error logs. I’ll be interested to see what’s going on there.

Given the rate of content creation by the client (especially in this Ditto newsroom) - if there’s some functionality that could mitigate the resource usage - I’d be very interested to add that to the bounty forum. Any input on possible solutions greatly received

The site is supposed to go live on Thursday so I may have to open that support ticket in any case.

Which version of Ditto are you using? If not the latest Ditto SVN version I’d try that pronto: http://ditto.modxcms.com/

Try placing these on pages: http://www.modxcms.com/modx-tags.html#p26-9 I hope it will give you some good insight.

Quote from: rthrash at Sep 25, 2007, 06:00 PM

Which version of Ditto are you using? If not the latest Ditto SVN version I’d try that pronto: http://ditto.modxcms.com/

I’m running a pretty up-do-date version of Ditto - as you’ll notice the Reflect navigation is somewhat different - the author of Ditto (Mark) put together a customised version of Reflect so that I could have the news navigation stacked that way.
I have just tested with the latest versions of ditto and reflect and I’m getting the very same issues - intermittent Error 500.

I’m guessing Ditto wasn’t set up to deal with so many items?

Quote from: zi at Sep 25, 2007, 08:25 PM

Try placing these on pages: http://www.modxcms.com/modx-tags.html#p26-9 I hope it will give you some good insight.

Thanks Zi. In between error 500’s I managed to get this output::

Query Time: 0.5235 s | Query Count: 26 | Parse Time: 10.4741 s | Total Time: 10.9976 s | Source: database

And I get this on re-loading the same page (the cache effect):
Query Time: 0.0698 s | Query Count: 1 | Parse Time: 4.0145 s | Total Time: 4.0843 s | Source: cache


Any further help/pointers greatly received.

Another weird thing I’ve noticed - is that when the news room does load - I can no longer navigate by the Reflect menu - it just sticks on current month/year Sept 07.

Before adding the extra 800 news items yesterday - the navigation was working fine.

The query string does update depending on the month / year you click, eg:



Which should show June 2007 - though it sticks on September 2007 :0 weird.

Ok, based on the cached file timing I see, time to investigate the siteCache file. How large is this file currently (see assets/cache/siteCache.idx.php)?

Though the Reflect specific problem makes me wonder if there isn’t some other bug related to that wreaking havoc here.