3 ms·

This will give developers leverage to ask for time to optimise, upgrade, and improve things they are not normally allowed to work on, as it will raise the discu

This will give developers leverage to ask for time to optimise, upgrade, and improve things they are not normally allowed to work on, as it will raise the discussion to the level of managers and the general public. However, do you think more could be done to make the default MySQL/PHP type configurations faster out of the box? If it is possible to speed up the default config of most websites on the internet, perhaps there is an easy win to be had.

moreira 7y ago
> However, do you think more could be done to make the default MySQL/PHP type configurations faster out of the box? I'm pretty sure that most slow websites aren't slow because their server-side rendering takes a long time. This seems to be mostly a front-end oriented thing (especially directed at pages that load MBs of JS); basically if the page doesn't adhere to all the front-end optimisation guidelines.
- _bxg1 7y ago
  The slowness described in the article isn't jank, but time-to-initial-load. Conceivably the initial client-side render could take a nontrivial amount of time, but in the vast majority of cases - just like for server-side rendering - it isn't a deciding factor. The real deciding factor is the amount of dependencies that have to be loaded. This includes JS, but usually the JS for ads/tracking is far larger than the JS for the actual UI, even on fully client-side-rendered sites.
acdha 7y ago
PHP and MySQL are pretty fast out of the box - and have been for a couple decades (a single server was well into hundreds requests per second by 2000). What’s slow are the frameworks on top of them, and a lot of that is going to require big changes since things like the WordPress plugin world or most of the JavaScript world have not had a great culture about monitoring and optimizing things. Simply moving this into the category of problems you can’t ignore would be positive - along with tracking data usage for mobile users on metered plans.

moreira 7y ago

> However, do you think more could be done to make the default MySQL/PHP type configurations faster out of the box? I'm pretty sure that most slow websites aren't slow because their server-side rendering takes a long time. This seems to be mostly a front-end oriented thing (especially directed at pages that load MBs of JS); basically if the page doesn't adhere to all the front-end optimisation guidelines.

_bxg1 7y ago
The slowness described in the article isn't jank, but time-to-initial-load. Conceivably the initial client-side render could take a nontrivial amount of time, but in the vast majority of cases - just like for server-side rendering - it isn't a deciding factor. The real deciding factor is the amount of dependencies that have to be loaded. This includes JS, but usually the JS for ads/tracking is far larger than the JS for the actual UI, even on fully client-side-rendered sites.

acdha 7y ago

PHP and MySQL are pretty fast out of the box - and have been for a couple decades (a single server was well into hundreds requests per second by 2000). What’s slow are the frameworks on top of them, and a lot of that is going to require big changes since things like the WordPress plugin world or most of the JavaScript world have not had a great culture about monitoring and optimizing things. Simply moving this into the category of problems you can’t ignore would be positive - along with tracking data usage for mobile users on metered plans.