Language INI files are extremely costly #38589
dgrammatiko
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
That sounds valid. Would be interesting to see numbers, that can give motivation to someone to code it.
Please do not run to the edges. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The language strings come as INI files. There's a cost of reading/parsing/converting to array for each of these files.
This can be done ONCE, after install/update/remove and save the file as a php returning an array. In short at runtime the app will have to only read a file and merge the array returned from the language file to the array of translation strings. The INI could stay as fallback. The load sequence also could be simplified. Bonus since the files will be .php they could benefit further from OPCache...
Why?
The current architecture is very inefficient both on terms of wasted cpu cycles and excessive energy consumption.
If you want to go one step further you could have per application (site/administrator) a file that has all the sys.ini files concatenated. It increases the memory but reduces I/O operations
Again this is touching architecture so something for @nibra @HLeithner @laoneo
Beta Was this translation helpful? Give feedback.
All reactions