Task #32758
closed
Cache result of JS and CSS file concatenation
0%
Description
Concatenating the JS and CSS files (esp. in BE) is very expensive (up to 6% of rendering time).
Even more expensive than checking for file modifications is are the string operations while figuring out, what to include (resolveBackPath, isValidPath etc.).
So to be precise: Of course, we do not concatenate it every time. It's only about figuring out, how the hash of the concatenated file is (this is based on the included file names and their modification times - and this is already expensive).
Files
Updated by Steffen Gebert over 12 years ago
- File 32758.diff 32758.diff added
Preliminary patch attached. Tricky parts missing: Cache clearing (on extension installation, what else?) and consequences for FE?
Updated by Markus Klein over 12 years ago
Shouldn't the *worker() functions be static?
Updated by Steffen Gebert over 12 years ago
Ah, no ;) I shouldn't call them statically ;)
Used the same approach to tune some other code in t3lib_div, that's why my brain was so static ;)
Updated by Mathias Schreiber over 9 years ago
- Category changed from Miscellaneous to Backend API
- Status changed from New to Accepted
- Assignee set to Jigal van Hemert
- Priority changed from Could have to Should have
- Target version set to 7.0
- PHP Version set to 5.5
can you check this in connection to the CSS-Splitter you added earlier?
Updated by Mathias Schreiber over 9 years ago
- Target version changed from 7.0 to 7.1 (Cleanup)
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Susanne Moog about 5 years ago
- Status changed from Accepted to Needs Feedback
- TYPO3 Version set to 4.5
@Jigal van Hemert Are you still working on this? Is the issue still valid?
Updated by Susanne Moog about 4 years ago
- Status changed from Needs Feedback to Closed
No answer for a long time, closing the issue.