AmigoJack wrote: ↑
Wed Dec 12, 2018 9:28 am
But the performance also dropped from 2.0 to 3.0, if you mind.
huh? 3.0 is ridiculously faster than 2.0.... Took a little digging to find it but here is some benchmarks.
https://area51.phpbb.com/phpBB/viewtopi ... 10#p171200
I'll have to have a word to see if can get someone to try Apache-bench on various server setups. However, this might be eye opener, with me having had a dig around on archive.org on a now dead phpBB I used to run, and had incarnations running phpBB 1.2.x, 1.4.x, 2.0.x and now testing 3.x (converted from 2.0.x obviously) on exactly the same hardware configuration (Dual Pentium III-S 1.26 GHz, 1.5GiB RAM & 2x 60GB HDDs in RAID1):
phpBB1.4.x (vanilla) = index.php in ~0.070 seconds
phpBB2.0.0-ish (without template cache) => index.php in ~0.500 seconds
phpBB2.0.5-ish (with template cache) => index.php in ~0.250 seconds
phpBB3.0 CVS (vanilla) => index in ~0.080 seconds
phpBB3.0 CVS (with eAccelerator) => index.php in ~0.016 seconds
Getting back to the OP I'm not so sure how you run opcache on shared host, rough guess is phpBB is using about 15 to 20MB of RAM for opcache. You might want to try seeing what some opcache stat tools tell you, I have been using this one:
There are some configurations that can be made to opcache,
. that will prevent opcache from checking the file on disk for changes. It's important to note that you need to clear opcache when you upload new php files. Conveniently, purging the cache in the ACP for phpBB invalidates all files in Opcache so they will be reloaded from disk.
On 3.2 topic view medium generation time is about 0.170s
Is that from the browser or phpBB's footer? Not sure what kind of times I'm getting from the actual script but that's what I'm getting from the browser.
“Results! Why, man, I have gotten a lot of results! I have found several thousand things that won’t work.”
Attributed - Thomas Edison