3 ms·

Lets try to take the discussion into something technically more interesting. WordPress is calling the database for most things which make things slow. I don't

Lets try to take the discussion into something technically more interesting. WordPress is calling the database for most things which make things slow. I don't know how things improved over the years but is there any trial for a hard or soft fork that tries to address this performance bottleneck? The last time I worked with WordPress was 5-6 years ago so I am not aware of the scene now. If there would be a fork resulting from this fiasco I hope it will focus on addressing that. Although WordPress registry and community is too big to change over a short or medium range.

ivanmontillam 2y ago
The current best practice for solving that is to flatten your WordPress installation in HTML files, or to use a WP cache plugin. Caches like CloudFlare also help a lot. I don't know the exact details about it, but that solves the bottleneck. Once pages are flattened they do not have to call the database again. There's also a flat-file CMS called FlatPress, but I was not able to reliably determine if it's a fork or not.