On Fri, 2015-11-27 at 21:35 +0100, Jan Ehrhardt wrote: > In most cases that is true. But not always: we have an application that > uses PHP for matching a lot of profiles with a couple of hundred job > opportunities. Despite a lot of optimizations it drills down to a single > PHP thread doing the bulk of the processing. We even chose a processor > with a high single thread score when we had to buy a dedicated server to > run this application, using these charts: > http://www.cpubenchmark.net/singleThread.html > > So anything that makes PHP using more cores would be very welcome. > Preferably it has to be transparent, i.e. without extra coding like > starting up more threads using the php threads extension.
Yes, there are cases where this might be useful, but it is also a notable complication of the implementation and in my opinion (feel free to disagree) PHP shouldn't do "everything" good, but solve the Web thing in the best way we can. There are other languages and tools for other things. So for a sensible evaluation: Take a "common" application, profile it, identify the areas which are relevant, create proof-of-concept implementation, compare under load. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
