3 ms·
Just to make sure: You built all binaries and linked libraries yourself, from scratch, with the same optimization settings, right?
by nanis 10y ago
Just to make sure: You built all binaries and linked libraries yourself, from scratch, with the same optimization settings, right?
- erichileman 10y agoThe binaries are from remi repo. We have a template we provision from. I used the same template on each virtual machine. PHP 5.4.45 (cli) (built: Sep 19 2016 15:31:07) PHP 5.5.38 (cli) (built: Nov 9 2016 17:32:11) PHP 5.6.28 (cli) (built: Nov 9 2016 07:04:38) The binaries are the same on each virtual machine. Are there build optimizations for E3/V5 vs E5/V2 that could make such a difference?
- erichileman 10y agoFound this and will try it: https://github.com/centminmod/centminmod/commit/755dd9e87eac10f54bda9379983f69a588305b23 https://github.com/centminmod/centminmod/commit/755dd9e87eac...
- cthalupa 10y ago>Are there build optimizations for E3/V5 vs E5/V2 that could make such a difference? Potentially, yes. Either way you're not comparing apples to apples using packages from a 3rd party repo built for a different system. Newer processors have different instruction sets (AVX is a big one). You'd want to make sure you're not only compiling it on each different platform, but also using a new enough compiler to support the instruction sets.
- erichileman 10y agoCorrect. We are going to build using the correct -march flags: https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html
- erichileman 10y ago>>gcc -march=native -Q --help=target >>march=silvermont gcc native thinks this e3 is silvermont, a low power SoC.
- erichileman 10y agoWe built 5.6 with -O2 -march=broadwell -mno=avx (had to remove, probably pecl ext issue). There was about a 15% performance gain. Nothing that would explain the large difference between E3 and E5.