hi,
first, i know this blog post is from 2018. 2018/02/12 - PHP As A Module
It makes me curious about the state of lsphp, however. I notice that remi's builds are not built as thread-safe (using --disable-zts flag on the ./configure script line i suppose). i've been using my own built lsphp for a long while now, for multiple reasons, but i had always built with --enable-zts set. my current builds are now using --disable-zts.
Does openlitespeed take advantage of PHP built thread-safe via LSAPI hooking of LSPHP?
Is building PHP as a module for OLS actually a thing still? (mod_lsphp)
i do build in a couple extensions statically (mysqlnd and mysqli (mysqli needs to be built in statically if mysqlnd is and you want to use mysqlnd as the driver for mysqli)). i'm still unsure whether to drop mysqli strictly for pdo_mysql, which i build shared. idk. but my host is 4 vcpu's and 8gb ram. i currently use lsphp in detached mode (1 instance, 30 children max/30 connections max), 1 thread for lshttpd. i use percona server for mysql 8.0 and redis 7.2, though i was having an issue setting sessions in redis, but the problem was with session config itself. going to try it again now. i was using almalinux 9.4 for a long time, but i finally got around to re-imaging with RHEL 9.5, percona mysqld 8.0, ols 1.8.2 from the repo, redis 7.2 from remi, lsphp 8.4 built from source branch PHP-8.4 with igbinary, phpredis, zstd, timezonedb sources pulled into ext/ and compiled shared. I'm mentioning this all because it might help determine whether i'd benefit from multi-threading lsphp.
Anyway, thanks in advance. That info is obviously outdated but i'm curious about whether building with zts would have potential benefits.
first, i know this blog post is from 2018. 2018/02/12 - PHP As A Module
It makes me curious about the state of lsphp, however. I notice that remi's builds are not built as thread-safe (using --disable-zts flag on the ./configure script line i suppose). i've been using my own built lsphp for a long while now, for multiple reasons, but i had always built with --enable-zts set. my current builds are now using --disable-zts.
Does openlitespeed take advantage of PHP built thread-safe via LSAPI hooking of LSPHP?
Is building PHP as a module for OLS actually a thing still? (mod_lsphp)
i do build in a couple extensions statically (mysqlnd and mysqli (mysqli needs to be built in statically if mysqlnd is and you want to use mysqlnd as the driver for mysqli)). i'm still unsure whether to drop mysqli strictly for pdo_mysql, which i build shared. idk. but my host is 4 vcpu's and 8gb ram. i currently use lsphp in detached mode (1 instance, 30 children max/30 connections max), 1 thread for lshttpd. i use percona server for mysql 8.0 and redis 7.2, though i was having an issue setting sessions in redis, but the problem was with session config itself. going to try it again now. i was using almalinux 9.4 for a long time, but i finally got around to re-imaging with RHEL 9.5, percona mysqld 8.0, ols 1.8.2 from the repo, redis 7.2 from remi, lsphp 8.4 built from source branch PHP-8.4 with igbinary, phpredis, zstd, timezonedb sources pulled into ext/ and compiled shared. I'm mentioning this all because it might help determine whether i'd benefit from multi-threading lsphp.
Anyway, thanks in advance. That info is obviously outdated but i'm curious about whether building with zts would have potential benefits.
