Answered Performance question with getResources

The site I am building will have around 100 installers each of which can be on one of three levels. The number of installers is likely to double in the next couple of months.

The list of installers need to be sorted primarily in the order of their installer level and then alphabetically but the site also allows for the installers to be filtered by region. For each installer level, the HTML output needs to be slightly different (change in colours and in some cases the information displayed).

Which is better from a performance basis?

Option 1:

Run a single getResources which needs a &tvFilters for the region, a &sortbyTV for the level and a &sortby the pagetitle and then use modifiers to in a single chunk to output the HTML for each installer level.

Option 2:

Run getResources three times (once per installer level) in the right order but will need a &tvFilters for the region but each would have their own HTML chunk which would eliminate the modifiers (but does not need to be sorted by installer level).

Right now all the installers are children to a single parent. With option 2, I could give them each there own parent which would reduce the amount of processing for the getResources but would complicate the admin a little bit.

So in essence, is it better to run one more complex SQL query and then modify the output or run 3 simpler SQL queries and have less modifiers?

I am using the latest Revo and the site is hosted on modxcloud.

Kind regards

James

Hm... it's beginning to sound like having it so easy to extend a modResource (or any other class relating to resources) will make TVs and a lot of plugins obsolete. It comes a lot closer to having categories of resources instead of tying custom features to a resource's template.

I'd like to think so, but you still need to be able to create a schema or DB table, and you need to be able to modify a bit of modExt-flavored HTML to add the extra fields to the Create/Edit Resource table. You also need to be able to create a JSON 'where' property for searching and it won't work with Articles.

I won't really know how hard it is to use ClassExtender until some more people try to adopt it. It seems easy enough for me, but I'm pretty familiar with it.

Another consideration is that at present NewsPublisher won't handle the extra fields. I think I have the solution to that in my head, but it probably won't be implemented until I see significant demand for it.

I can see that coming. modGalleryResource, modMediaSourceStaticResource, as well as a hundred variations on modBlogResource or modNewsResource. I never did like Articles.

I didn't play with ClassExtender, yet.
But I think it should be possible to combine MIGXdb and ClassExtender.
So you could use TV-input-types and configure Tabs and Fields with MIGXdb.

I think I can see where blending the two would be useful. Instead of nested MIGx or MIGXdb TVs, you could have a custom Resource Type with a single MIGx TV. This would be much faster, not to mention easier to keep track of what is where.

I'm curious to see how the two might work together. It ought to give faster searching and sorting.