Just out of curiosity - how/why are you accessing over 400 resources in a single page load?
Because, that is how RO.IDEs works. An AJAX call of about .25 secs accesses about 30 pages. An full page load accesses about 400 (currently). They are "micro-resources" so that my code editing is super fast and has a lot of benefits. My ModX is faster now than it was before I made RO.IDEs...
If you need further information, my CSS is comprised of about 300 micro resources. My snippets are another 75. My Plugins are approximately 25. It certainly doesn't appeal to everyone, but the thread is here:
https://forums.modx.com/thread/77735/ro-ides-editor-and-framework-for-modx-revolution-2-2
I think your best bet might be to look at extending Articles, as that will at least provide a way to manage the resources in the back end.
I thought about that, but I wasn't sure if you could extend an AddOn's Custom Resource Class. Looks like I'll have look into that.
And that's where MIGxDB would shine.
I've seen a bit about MIGx, and a little about MIGxDB. I'm not gathering how I can use it effectively for some reason. Would you care to elaborate, sottwell?
Resources carry a lot of overhead that you might not need and MODX does a lot of parsing of things like pub_date, unpub_date, etc. when loading, saving, and preRendering that might be unnecessary.
You only have to worry about the overhead, if you do a full SELECT *. And you only have to worry about the parser when you invoke it. That said, I do no direct database manipulation, I simply ask $modx for what I want and leave it at that.
A custom DB table (with enough capacity in the fields) and only the fields you need might be a better option.
I thought about that, but that would not allow me to edit my CSS, JS and PHP in the same Resource tree. As it stands, I only query the fields I want, (pagetitle, description, content, introtext, published), have full parenting, more functionality, and can use a single TV to alter as many CSS, JS and PHP parts as I want, in real time processing. And my pages load faster than they did when I had 30 resources and several Snippets with no JS and a huge CSS.
Pending some thoughts from sottwell (hopefully) on MIGxDB, I'll probably just have to get the site up and fix scalability issues later.
[ed. note: fuzzicallogic last edited this post 14 years, 2 months ago.]
