Is PHP7 release stable? #213
Comments
|
Hello, there is no release for PHP7 yet. I am currently working on resolving issues with PHP7 and cleaning up the code. Is the persistent connection issue easy to reproduce? I'll take a look as soon as possible Thanks, |
|
Aha, that's great i'll see about reproducing the issue and prepare some code |
|
Hi Mikko, we looked more into the issue... Good thing is that the spike problem seems to be networking related. We have just installed php7/lighty on this server and it seems we have some switch problems. That's what was causing spikes in connection times... sorry for confusion. Now for the segfault issues, we were able to eliminate it by switching to memcache (not d) module found here So the only thing i know for now ...
If i'll find anything else that might help diagnosing issue - will post here. Thanks. |
|
@mkoppanen Only waiting for stable release! My unit tests are passing! |
|
Let me know if there's anything I can do to help with PHP 7, @mkoppanen ! |
|
👍 ehehhe, oh, the waiting is killing me. |
|
with PR #214 I am unable to reproduce the persistent connection segfault. In my local environment persistent connections seem to work as expected and valgrind isn't complaining. Can you try this branch and see if it solves your issues? Thanks, |
|
Hi Mikko, sorry for waiting, we were able to do some quick tests with recent code (i saw #214 is merged in php7 branch), with persistent connections - no longer segfaulting, so it seems fixed. |
|
Any news or timeline for a PHP7 supporting release? |
|
@ralfbecker You can compile it using the php7 branch. See my comment on this issue: #194 (comment) |
|
@mkoppanen JFTR I got one user reporting BC break in 3.0.0b1, but he refused to report it here and claims the BC break in 3.0.0b1 is deliberate. Are you aware of any BC breaks in 3.0.0b1 (latest git), I haven't found anything in the git log that would suggest so? |
|
@oerdnj, there is an intentional backwards compatibility break with cas token parameter in certain calls. |
|
Is that documented anywhere? Or a ticket for it? |
|
Ah just saw, it's in Any plans for the |
|
@mkoppanen what can I or my company do to help speed up the release of this? I understand you are a busy guy and thank you for all your work here. We are excitedly awaiting this package so we can start using php7 in production and would like to help any way we can. |
|
if you got time to write a bit better changelog based on the work on git commits. Especially detail the backwards compatibility break in cas params better (the reasoning). Other than that it's good to go. |
|
Hi! Is there a release date for the PHP7 version? Thank you |
|
We are eagerly awaiting this release. Let me know how we can assist. |
|
Can you please merge #232 and the following PRs with docs @mkoppanen so I or others can continue work on the changelog? |
|
I've been trying to take a stab at the changelog, @mkoppanen, but unfortunately, the most important changes are all part of one massive commit, a930b41, with no descriptive commit message or comments. |
|
Bump, any news ? |
|
Hey guys! The #250 issue looks closed, so... any news about stable release with php7 support? Our OPS team refuse to install the unstable version nor any third party builds so we are kind of stuck with migration to php7 because of memcached extension. |
|
Same here, missing Memcached support stalls PHP 7 migration :( |
|
is the release of the 7 version a time / money issue? It seems like a lot of people need this to migrate to 7, so if all these people would put some money in a jar we could pay someone to do the work. Is setting up a donation thing a good idea? |
|
or this because everybody should move to Redis? Oh nooo |
|
I've found the |
|
@colepatrickturner what build? Can you reproduce so as to open a ticket? Your comment is raining on my parade as is. Also, curious where does your php-memcache comes from? Port by kaltura? |
|
PHP (FPM) Version: 7.0.11-1+deb.sury.org What I experienced: I cross-checked this directly with the memcached daemon |
|
@colepatrickturner The latest release in the PPA should be I have also just uploaded the currect php7 HEAD build, so even better try with |
|
@oerdnj the machine I'm using is amd64 which has failed builds for anything greater than 3.0.0a1-13. I'll see if I can reproduce it on another machine and then build from source to the latest version. P.S. thank you for providing packages! |
The Memached get functions stopped using references to cas_token(s) so that get() be mocked easily. See https://github.com/php-memcached-dev/php-memcached/pull/271/files php-memcached-dev/php-memcached#213 (comment)
The Memached get functions stopped using references to cas_token(s) so that get() be mocked easily. See https://github.com/php-memcached-dev/php-memcached/pull/271/files php-memcached-dev/php-memcached#213 (comment)
|
Not to criticize or anything, but for having run both phpredis and this memcached extension in production with PHP 7.0 for some months, with a relatively simple SET/GET usage, both have their issues. In my opinion "switching to Redis" might not necessarily be the right solution, see phpredis/phpredis#429 - I have been bitten by that one, with some fairly nasty consequences. Right now I'm still seeing some minor issues with the memcached extension, but at least the issues seem visible (PHP Warnings are triggered) and memcached scales much better than redis on a single system with simple SET/GET usage (Redis is single fork, single thread and easily saturated a single CPU core in my environment). I'm hoping to have time to debug our issues soon, and report details here, but in the meantime it could be a nice thing to get a proper release of the current code on the php7 branch, maybe marked as beta for now. |
|
Good idea to release beta, because it will reach more installs and more testers.
Jan Pobořil
http://honza.poboril.cz/
21. 12. 2016 v 16:01, Matthias Saou <[email protected]>:
… Not to criticize or anything, but for having run both phpredis and this memcached extension in production with PHP 7.0 for some months, with a relatively simple SET/GET usage, both have their issues. In my opinion "switching to Redis" might not necessarily be the right solution, see phpredis/phpredis#429 - I have been bitten by that one, with some fairly nasty consequences.
Right now I'm still seeing some minor issues with the memcached extension, but at least the issues seem visible (PHP Warnings are triggered) and memcached scales much better than redis on a single system with simple SET/GET usage (Redis is single fork, single thread and easily saturated a single CPU core in my environment).
I'm hoping to have time to debug our issues soon, and report details here, but in the meantime it could be a nice thing to get a proper release of the current code on the php7 branch, maybe marked as beta for now.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hi Guys, I want to invite you to test my memcached - like server written in go available at: Basically in my company we were using memcached modified by me for a long time (like 3-4 years), because of bugs with PHP7 (and also we need something a little different than memcached), i decided to write my own version... It's used in production for about 200 days without restart, it has much better GC, configurable auto-rebalance which is able to move items between slabs, snapshots, tcp optimizations for high MTU, optimizations for high number of CPU cores, etc. It has native PHP client using TCP sockets, and the server works on TCP, UDP and HTTP. Easy to install using composer. The new version has some nice features like sharding and replication for all operations. Sharding and replication is tested using phpunit tests, but not yet in production, we'll be testing that too, soon. If smoeone has any questions let me know. |
|
Comment of @slawomir-pryczek seems like a spam. (This project is PHP client for Mencached, not server.) |
|
@iBobik It looks like both a memcached replacement and a native PHP client for an in-memory key-value store. If it's spam then the redis conversation is too. |
|
@jrchamp yes thanks for the comment, the project is server and client. To help people that have issues with memcached and want to try something what is more like memcached than redis/mongo, and has all features which are missing from simplified memcache extension (which is very good but lacking some features like atomic ops with CAS), plus want good support for very dynamic data (different size, TTLs, etc.). @iBobik You're here just to say "good idea" and link to your homepage... then, magically i'm "spamming" :) Uh, okay ;) |
|
Because he replied to the issue via email and now stop spamming this issue with other projects please. |
|
So, 5.6 officially loses support in 2 days, 7.0 has been out for 2 years, and still no stable version of this extension, nor any clear answers on what still needs to happen or how we can help? It's an OSS project after all. I'm more than willing to invest some time in getting this to a stable release. |
|
@Intrepidity What are you talking about? PHP 5.6 is security supported until 31 Dec 2018 (e.g. two more full years) and PHP 7.0 was initially released 1 year ago (not two). |
|
@Intrepidity I have recently spoken with a guy that wrote similar extension for his company as they were having issues with PHP7... you may give it a try, if you need memcached as he seemed very capable |
|
So what is the reason for such delay? |
|
The 3.0.0 release will be released Real Soon Now. I'm cleaning up the tickets in preparation. |
The Memached get functions stopped using references to cas_token(s) so that get() be mocked easily. See https://github.com/php-memcached-dev/php-memcached/pull/271/files php-memcached-dev/php-memcached#213 (comment)
add php 7.0 & 7.1 version Manque l'extension memcached, pas encore de release disponible pour php7, juste une branche sur github pour le moment. Cf : php-memcached-dev/php-memcached#213 docker-library/php#317 Merci de review. See merge request !14
Hi Guys,
I tried to switch to php-memcached on a service where we have like 20-30k request/s and it seems that PHP7 memcached release is having some issues... basically when using persistent connection mode it segfaults like crazy. I tried to switch to normal connections but then other memcached clients using old library under php5.6 were having issues to connect (maybe connections are not fully closed?)
We also made a simple debugging script, on pconnect it segfaults and loose key values (even if key is in cache it randomly returns empty), on normal connect it's much slower than memcache and unstable... connect->set->get takes about 1-30 ms, on the old setup (memcache/php) extension it's preety constant at 1-4ms.
Up to some point it works ok (we build a cluster like setup where we can control traffic send to all nodes), but after traffic gets higher it starts to make issues.
Can this be somehow related to connection handling and are you aware of this issue?
The text was updated successfully, but these errors were encountered: