Revo 2.0.x slow performance - can we diagnose?

33 Posts

leoandrews Reply #21, 15 years, 2 months ago

Further to the above, I found the snippet and implemented but it seems to have made no difference. Error log says
Before:

[2011-07-23 03:24:40] (ERROR @ /index.php) modSnippet: Wayfinder executed in 1.0814 s

After:

[2011-07-23 03:27:26] (ERROR @ /index.php) modSnippet: Wayfinder executed in 1.6937 s
[2011-07-23 03:30:28] (ERROR @ /index.php) modSnippet: Wayfinder executed in 1.0324 s
[2011-07-23 03:32:36] (ERROR @ /index.php) modSnippet: Wayfinder executed in 1.1074 s

The call is:

[[!Ex? &tElement=`Wayfinder` &startId=`0` &outerClass=`` &firstClass=`` &hereClass=`` &lastClass=``  
&rowTpl=`wfFooter` &fullLink=`TRUE` &startItemTpl=`wfFooterStart` &hereTpl=`wfFooterHere` 
&displayStart=`TRUE` &includeDocs=`[[!listChildren? &parent=`0` &depth=`1`]]` &cacheResults=`1`]]

Ex is the Executioner
listChildren is listChildIds

☆ A M B ☆
2,475 Posts

Everett Reply #22, 15 years, 2 months ago

Sorry, I think it was a custom thing. Here’s the simple Snippet:

listChildIds

<?php
return implode(',', $modx->getChildIds($parent, $depth));
?>

Hosting stuff: http://fireproofsocks.com/
Coding stuff: http://craftsmancoding.com/
Blog stuff: http://tipsfor.us/

33 Posts

leoandrews Reply #23, 15 years, 2 months ago

Quote from: Everett at Jul 24, 2011, 12:58 AM

Sorry, I think it was a custom thing. Here’s the simple Snippet:

listChildIds
<?php
return implode(',', $modx->getChildIds($parent, $depth));
?>

That’s what I’ve got here too - but as you can see, above, it seems not to have cured it.

33 Posts

leoandrews Reply #24, 15 years, 2 months ago

Bumping this. Any thoughts as to why this is running so slowly?

MODX Staff
10,725 Posts

opengeek Reply #25, 15 years, 2 months ago

Wayfinder could use some optimization no doubt. Just make sure you cache all your Wayfinder calls. Or if you can’t cache them and have simple, flat menus, try using getResources instead.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

33 Posts

leoandrews Reply #26, 15 years, 2 months ago

Thanks, I’m doing what I can now to eliminate Wayfinder and replace with getResources. But here is a thought... for the 2.0.8 site, here are the cache settings - can you spot anything which could be optimised?

MODX Staff
10,725 Posts

opengeek Reply #27, 15 years, 2 months ago

I would disable cache_db — it is not working well in 2.0.x anyway and adds overhead for no reason if you are using a database on the same machine as the web server. Otherwise, I recommend upgrading to 2.1 for the overall caching improvements it contains.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

33 Posts

leoandrews Reply #28, 15 years, 2 months ago

Quote from: OpenGeek at Jul 28, 2011, 12:33 PM

Otherwise, I recommend upgrading to 2.1 for the overall caching improvements it contains.

I wanted to (and indeed attempted the upgrade) but had to rollback due to getResources not working with 2.1.2

MODX Staff
12,272 Posts

Ryan Thrash Reply #29, 15 years, 2 months ago

getResources should work just fine with 2.1.2 and 2.1.3.

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

MODX Staff
10,725 Posts

opengeek Reply #30, 15 years, 2 months ago

Quote from: rthrash at Jul 29, 2011, 11:57 AM

getResources should work just fine with 2.1.2 and 2.1.3.

There were issues in 2.1.2 with core parsing of nested non-cacheable tags that affected certain uses of many components, including getResources, but this was fixed for 2.1.3.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek