sasiko Posted December 5, 2015 Posted December 5, 2015 ips3.x wont work on php 7. im on php 7 and ips 4.1.4.1 works fine for me so far. i have forum and ipsdownload installed
Gary_J_Wright Posted December 5, 2015 Posted December 5, 2015 currently got a 'test' board 4.1.4.1 (of my live board ) on a LEMP server using php7.0.0. nginx 1.9.7 and mariadb 10.1
sasiko Posted December 5, 2015 Posted December 5, 2015 @Lindy @Charles would love to see a blog entry in future where you benchmark php 7 on ips 4 and make a comparison with php 5.6
Colonel_mortis Posted December 5, 2015 Posted December 5, 2015 I've been running some very rudimentary benchmarks using a fresh install of IPS on a fresh install of the WAMP stack using PHP 7 vs PHP 5.5.30, and got reasonable improvements in performance, down from 193ms to 168ms when loading the forum index (100ms of that is connecting to the DB), as measured by XDebug, and down from 543 to 449ms when loading All Activity, again spending 100ms connecting to the DB.
bashy Posted December 18, 2015 Posted December 18, 2015 On 12/5/2015 at 8:56 AM, maidos said: ips3.x wont work on php 7. im on php 7 and ips 4.1.4.1 works fine for me so far. i have forum and ipsdownload installed I'm currently using php7.0 and IP.Board 3.4.6 I had to update some files but there weren't that many that required changing. Of course IonCube isn't out for php7 yet (I did check and not sure if 5.6 works on 7.0) so you can't use Nexus on IonCube etc.
Rheddy Posted December 18, 2015 Posted December 18, 2015 This is being discussed here: https://community.invisionpower.com/topic/424093-php-7-support/
bashy Posted December 18, 2015 Posted December 18, 2015 @Morisato Sadly some of us aren't active customers so we can't see it. It's good to show people who don't want to upgrade how to use php7 and IP.Board v3.x
Brian K. Posted December 20, 2015 Posted December 20, 2015 To those that saying that it works fine, have you guys checked php7.0-fpm.log ? I am seeing quite a lot of these WARNING: [pool www] child 21542 exited on signal 11 (SIGSEGV) after 268.798066 seconds from start disabling opcache seems to dramatically decrease the SEGV errors but not resolve completely. Also, system/3rd_party/pop3/pop3.class.inc got some ereg and eregi calls which are translated to errors in php 7.
Pierrickfacex2 Posted February 18, 2016 Posted February 18, 2016 On 20/12/2015 at 8:19 PM, Brian K. said: To those that saying that it works fine, have you guys checked php7.0-fpm.log ? I am seeing quite a lot of these WARNING: [pool www] child 21542 exited on signal 11 (SIGSEGV) after 268.798066 seconds from start disabling opcache seems to dramatically decrease the SEGV errors but not resolve completely. Also, system/3rd_party/pop3/pop3.class.inc got some ereg and eregi calls which are translated to errors in php 7. I also have a lot of those errors... Since December 20, did you find a solution ?
RevengeFNF Posted February 18, 2016 Posted February 18, 2016 Are you in the last version 7.0.3? Since 7.0.2 that i don't those errors in the logs.
Pierrickfacex2 Posted February 18, 2016 Posted February 18, 2016 Interesting... Yes I'm on PHP 7.0.3 but the Dotdeb version of it.
Aurélio "Baboo" Posted February 29, 2016 Posted February 29, 2016 My discussion board was 3x faster with PHP 7.0.3 compared with PHP 5.6.x and the only problem was Error EX2 when trying to access profile pages.
sobrenome Posted February 29, 2016 Posted February 29, 2016 1 hour ago, BABOO2016 said: My discussion board was 3x faster with PHP 7.0.3 compared with PHP 5.6.x and the only problem was Error EX2 when trying to access profile pages. How have you measured the speed comparison? Just by guess or with new relic, for example...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.