Quote from: Everettg_99 at Jul 06, 2013, 11:44 AMNo difference whether they are static files or not? That definitely sounds like a server issue then. Usually I avoid putting JS or CSS files into MODX because of the overhead of having PHP render the files, but I understand there are cases where it's quite useful.
How big are these files? If you copy the static files over to a vanilla server, how fast do they load?
I'm still testing, but the results turn out to be highly variable. Contrary to what I told Ben above, a static file sometimes is better. But only sometimes, and not for any obvious reason.
For instance, I have a 1.5kB Javascript loading out of the database (actually out of the MODX cache, I presume) with a 1080ms wait time, and that same file loads with a wait time of about 150ms as a static file. But I also have a 15kB CSS file with quite a few calls to chunks that's loading out of the database with a wait time of just 52ms. That's quicker than my static Javascript ...
Even stranger, if I get my databased Javascript as the sole element in a getResources call, then the wait time goes down to 206ms, barely more than the static files. If I put all my databased CSS into a getResources call, then the wait time on that file is similarly low - 215ms. Indeed, using getResources to call my CSS and JS, I can get the page load time (as reported by Pingdom) down to 1.8 seconds, which is nearly top-quartile.