Live data from Hacker News

A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

github.com

11–20 of 22 posts

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#11
post #10

I'm curious on the goal of releasing software like this, it's making some crazy claims right out of the gate, but is obviously not production ready or battle hardened. There's some reasonably obvious security issues and not a single test of any kind in the project.

I could understand your criticism if this was link to a flashy marketing page or a blatant attempt to sell something - but this is a github repo with an MIT license, what exactly is the problem? I have no particular interest in using this piece of software, but I would still celebrate and defend the notion that people can have little ideas like this, get something working and then share it with others to move forward…

I'm questioning what the purpose is of pushing it at this point in the project lifecycle. It may not have a fancy website but it is making flashy marketing claims in that readme. How about being upfront about the maturity of the project before making the kind of comparisons that it does.

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#12
post #10

I'm curious on the goal of releasing software like this, it's making some crazy claims right out of the gate, but is obviously not production ready or battle hardened. There's some reasonably obvious security issues and not a single test of any kind in the project.

I could understand your criticism if this was link to a flashy marketing page or a blatant attempt to sell something - but this is a github repo with an MIT license, what exactly is the problem? I have no particular interest in using this piece of software, but I would still celebrate and defend the notion that people can have little ideas like this, get something working and then share it with others to move forward…

I mean this thing is "Part of the Qbix platform" and there is an offer to sell services related to the "Qbix platform"

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#13

I'm curious on the goal of releasing software like this, it's making some crazy claims right out of the gate, but is obviously not production ready or battle hardened. There's some reasonably obvious security issues and not a single test of any kind in the project.

The goals are several:

1. To share an innovation we developed for ourselves, that can help the wider PHP community (after all, 80% of the Web still runs on PHP!)

2. To pioneer a new approach that can help a bunch of people, like Caddy or FrankenPHP had once pioneered its own approaches

3. To show that PHP by itself can be enough to not only build a decent web server, but actually surpass NGINX together with PHP-FPM both in memory and speed, which surprised us. The memory particularly turns out to be the bottleneck and Qbix Server finally helps solve the 10K issue for PHP!

4. To make a new and very simple way to cleanly build websites and APIs that leverage both HTTP Requests and WebSockets: simply drop appropriately named files in the right places! It is optionally opinionated so the shapes of new codebases using the server, instead of all being ad-hoc, can be standardized along the same lines our own are.

5. To get feedback from the HN community. Speaking of that:

Could you please list the reasonably obvious security issues, so they can be fixed?

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#14
post #3

I wonder if it would be possible to run Wordpress on this. The issue with Workermen or Swoole is that they doesnt provide request data through globals and some headers are absent which Wordpress is a heavy user of.

Should absolutely be possible, yes. What headers are usually missing?

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#15
post #10

Earlier quoted context omitted.

I could understand your criticism if this was link to a flashy marketing page or a blatant attempt to sell something - but this is a github repo with an MIT license, what exactly is the problem? I have no particular interest in using this piece of software, but I would still celebrate and defend the notion that people can have little ideas like this, get something working and then share it with others to move forward…

I'm questioning what the purpose is of pushing it at this point in the project lifecycle. It may not have a fancy website but it is making flashy marketing claims in that readme. How about being upfront about the maturity of the project before making the kind of comparisons that it does.

Every day HN receives submissions like this, albeit usually as "show HN" posts, but not always. One could argue it's literally what HN is here for.

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#16

Earlier quoted context omitted.

I'm questioning what the purpose is of pushing it at this point in the project lifecycle. It may not have a fancy website but it is making flashy marketing claims in that readme. How about being upfront about the maturity of the project before making the kind of comparisons that it does.

Every day HN receives submissions like this, albeit usually as "show HN" posts, but not always. One could argue it's literally what HN is here for.

> If you're sharing your own work and there's a way to try it out, put "Show HN" in the title. Make sure you've read the Show HN guidelines: https://news.ycombinator.com/showhn.html.

:shrug:

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#17
post #13

I'm curious on the goal of releasing software like this, it's making some crazy claims right out of the gate, but is obviously not production ready or battle hardened. There's some reasonably obvious security issues and not a single test of any kind in the project.

The goals are several: 1. To share an innovation we developed for ourselves, that can help the wider PHP community ( after all, 80% of the Web still runs on PHP! ) 2. To pioneer a new approach that can help a bunch of people, like Caddy or FrankenPHP had once pioneered its own approaches 3. To show that PHP by itself can be enough to not only build a decent web server, but actually surpass NGINX together with PHP-FPM…

May I suggest opening issues on the repo if you're keen for feedback?

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#18
post #6

At the expense of being unreachable if a single client does not play nice?

Not at all. You are probably thinking of evented programming that happens in Node, Swoole or FrankenPHP. Qbix server makes sure each PHP process is isolated, so you also don’t leak any memory or secrets across requests. Out of all runtimes powering web servers today, I like PHP the most for its shared-nothing architecture, preventing a whole lot of security bugs by default. I think making it evented for HTTP is clutc…

You (well your LLM of choice) doesn't answer the asked question. Maybe I'm stupid and there is an answer in this text, but I can't see it.

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#19
post #13

Earlier quoted context omitted.

The goals are several: 1. To share an innovation we developed for ourselves, that can help the wider PHP community ( after all, 80% of the Web still runs on PHP! ) 2. To pioneer a new approach that can help a bunch of people, like Caddy or FrankenPHP had once pioneered its own approaches 3. To show that PHP by itself can be enough to not only build a decent web server, but actually surpass NGINX together with PHP-FPM…

May I suggest opening issues on the repo if you're keen for feedback?

They are open. Can you not submit an issue?

Also, can you please list the obvious security vulnerabilities here?

Re: A PHP server that can handle 10x as many concurrent requests as Nginx+PHP-fpm

#20
post #6

Earlier quoted context omitted.

Not at all. You are probably thinking of evented programming that happens in Node, Swoole or FrankenPHP. Qbix server makes sure each PHP process is isolated, so you also don’t leak any memory or secrets across requests. Out of all runtimes powering web servers today, I like PHP the most for its shared-nothing architecture, preventing a whole lot of security bugs by default. I think making it evented for HTTP is clutc…

You (well your LLM of choice) doesn't answer the asked question. Maybe I'm stupid and there is an answer in this text, but I can't see it.

I wrote that answer with my own fingers on my iPhone
Post reply on HN