phpBB 3.1 load

[Nicofuma]

actually you are not talking about the same thing because Google speed measure the user loading time which is mostly dependent on the assets where opcache works only on the php side.

So about Google speed the main issue is with the browser cache and that's can't be fixed on phpBB side without having to pipe all the files through php to set the right header.

[DavidIQ]

I've run 3.0 and 3.1 now. Without a doubt 3.1 is slower than 3.0. Also, if you run a 3.1 forum through Google Speed test site as a benchmark, it'll usually come back with pretty bad results for speed, and no matter which 3.1 forum you run through it. They all tend to get poor results on speed.

https://developers.google.com/speed/pag ... tab=mobile

Same "poor" results for Xenforo (paid software):
https://developers.google.com/speed/pag ... ab=desktop
And MyBB (open source software):
https://developers.google.com/speed/pag ... ab=desktop

Also the results against a 3.0 site are more or less the same as you posted. Not saying the information isn't useful but seeing it compared against other sites makes it apparent that getting to the "green" on Google's own criteria seems to be quite difficult and maybe even unrealistic (plus it's their own criteria...they're not the czars of the internet...). Even one of their own sites rates "poor" against their own ratings:
https://developers.google.com/speed/pag ... mythbox%2F

This is all quite different from what is being discussed anyways.

[JoshyPHP]

I'm talking about PHP plugins like http://php.net/manual/en/intro.opcache.php

Ok, so you're talking about opcode caches. I didn't know that memory_get_usage() included the memory used by opcodes. I guess it makes sense to include it after all.

it's useless in a dev environment since any code changes won't show (because it's using whatever was cached )

If you set opcache.revalidate_freq to 0 it should show immediately.

[Nicofuma]

I'm talking about PHP plugins like http://php.net/manual/en/intro.opcache.php

Ok, so you're talking about opcode caches. I didn't know that memory_get_usage() included the memory used by opcodes. I guess it makes sense to include it after all.

Actually memory_get_usage() show the memory allocated by the zend allocator and everything in php (the php core and the extensions) should use the zend allocator except in some rare case (when you want to use shared memory per example or when you are using a third party library which is relying to another allocator (the native mysql library provided by Oracle per example))

[Volksdevil]

A lot of this is way over my head, but I certainly found 3.1.x to be a lot slower than 3.0.12 as soon as I upgraded. It only got worse with extensions etc, but I think I'm definitely back down to an acceptable speed now with lots of tweaking/better host/cloudflare. If the coming updates speed things up a bit more then great.