and it just seem like a waste not extracting the fastest version, especially taming wp datatransfers (apart from plugins).
I have no clue what you said there. What “fastest version” are referring to?
And we can test until we have a stable version, but I can’t find any info what happens once you have a customized superfast wp installation file.
Again, I don’t get what you mean by “superfast WP installation” file here. Customized installation file? And whatever that is, I guess “what happens” will depend on the “customization” you did.
Whatever you do, do not edit the WordPress core files… as
1) You’ll lose all your changes when you update WordPress
2) 3rd-party plugins may not play nice with your core customizations.
Except in some rare edge cases, any performance gain is going to come from how you use the provided WordPress functions in your custom theme or plugin — like the kinds of queries you make, and not in tweaking the core functions themselves.
That’s what the post you linked to is all about: optimizing the queries you make in your theme or plugin. It’s not about changing WordPress itself.
From the article:
WordPress, one of the most popular publishing platforms, has stood the test of time and now powers a significant portion of the web. Sadly, its reputation is plagued by claims of poor performance and complexity with scaling. However, the root causes of such performance issues are often bad code and poorly implemented plugins and themes.
… and concludes by saying:
From the above, it is clear that the root causes of poor performance in WordPress are bad and inefficient code. However, WordPress provides all the necessary functionalities through its various APIs that can help us build much more performant plugins and themes without compromising the speed of the overall platform.
Good luck!