You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This caused by usage of new/delete operators that uses malloc/free instead of emalloc/efree that ZendAPI provides
PalettedBlockArray objects bypasses ZMM and this causes noticable incorrect memory consuption calculation in PHP
^ You can also just type "status" in Console on Windows and compare memory usage with taskmanager
That problem also may cause slight perfomance degrade but I dont sure about it
Any comments on this or we just should ignore this problem?
The text was updated successfully, but these errors were encountered:
I'm aware of the issue, but it's complicated to fix and probably not worth it. Performance is pretty much irrelevant considering the low frequency of allocations.
Using ZMM comes with its own problems such as thread sharing restrictions, which, considering that I'd had plans to enable sharing PalettedBlockArrays between threads without copying, is a restriction I don't like.
I'll also point out that PHP memory usage reporting is basically useless in PM anyway since it doesn't count memory from anything but the current thread. You have to look at system memory stats anyway. We don't do this on Windows because there's a significant lag time for the commands needed to retrieve the stats.
This caused by usage of new/delete operators that uses malloc/free instead of emalloc/efree that ZendAPI provides
PalettedBlockArray objects bypasses ZMM and this causes noticable incorrect memory consuption calculation in PHP
^ You can also just type "status" in Console on Windows and compare memory usage with taskmanager
That problem also may cause slight perfomance degrade but I dont sure about it
Any comments on this or we just should ignore this problem?
The text was updated successfully, but these errors were encountered: