Answered getResources: I need more speed

I have at getResources call that looks like this:



There can be up to 150 children of the resource that it need to list.

Right now (after the page has been cached)it takes around 1,5-2 sec. in pure server waiting time (on modx cloud) for the list to be generated, that's a long wait when the content hasn't even started loading yet.

Does anyone have any ideas for how I can optimize the load time? (Skipping the TV's isn't a option, it has already been limited to the ones in the list)

Edit: Using modx 2.2.5 on modxcloud.com with latest versions of getPage and getResources. [ed. note: MathiasD last edited this post 13 years, 10 months ago.]

Once cached, these should be taking milliseconds to render. Are you executing uncached Snippets in your tpl( s )?

Quote from: opengeek at Dec 03, 2012, 08:49 AM

Once cached, these should be taking milliseconds to render. Are you executing uncached Snippets in your tpl( s )?

Only the getPage snippet, which as I understand it must be uncached.

I tried isolating the getPage/getResources call on a empty template and call it from there - that reduced the time. I then found the getPage cache setting in my properties(see attached) that was set for no. I changed it to yes, and then (on the empty template) the call above has a php time on around 350ms when coming from cache - which is acceptable to me. But I'm not sure if changing the getPage cache setting has a unfortunate effect? Everything seems to be working fine.

getPage has to be uncached so that it can generate subsequent pages of results. As long as you only have one page of results you won't see the problem, but if you have more than one you'll always only get that first page since the cached snippet no longer exists; it's been totally replaced by its initial output.

Quote from: sottwell at Dec 04, 2012, 03:22 AM

getPage has to be uncached so that it can generate subsequent pages of results. As long as you only have one page of results you won't see the problem, but if you have more than one you'll always only get that first page since the cached snippet no longer exists; it's been totally replaced by its initial output.

Hmm - yes, I see what you mean. On pages that isn't a container the ?page=2 returns the first page as well. On pages that is a container, and thereby ends with a trailing /, getpage still works fine...