Hi all,
We have an in-house php script that processes images. Been running it for years. It forks itself a number of times to increase the amount of images we can process per second. 13.2 has been running great. When upgrading to 13.3 or 14.0, the php forked processes all end up leveraging the came cpu core, and that slows us waaay down.
I had a 13.2 userland, and 13.3 kernel and the issue does not occur.
Using a 13.3 userland and 13.3 kernel the issues DOES occur. Same with a fresh install of 14.0 userland/kernel.
Leveraging the pkg php82 from 13.2 land on 13.3 or the 13.3 pkg php82 does not matter, both show the same issue.
Something in the userland/libraries with 13.3 apparently is restricting forked php processes from leveraging any additional cpu cores. Any ideas where/what/how/why?
Thanks!
We have an in-house php script that processes images. Been running it for years. It forks itself a number of times to increase the amount of images we can process per second. 13.2 has been running great. When upgrading to 13.3 or 14.0, the php forked processes all end up leveraging the came cpu core, and that slows us waaay down.
I had a 13.2 userland, and 13.3 kernel and the issue does not occur.
Using a 13.3 userland and 13.3 kernel the issues DOES occur. Same with a fresh install of 14.0 userland/kernel.
Leveraging the pkg php82 from 13.2 land on 13.3 or the 13.3 pkg php82 does not matter, both show the same issue.
Something in the userland/libraries with 13.3 apparently is restricting forked php processes from leveraging any additional cpu cores. Any ideas where/what/how/why?
Thanks!