42 ms·
Why? While Nxweb looks very promising, my first question would be 'Why should I use it over eg Nginx?' It would be helpful to have some direct comparison to ot
by glossyscr 11y ago
Why?
While Nxweb looks very promising, my first question would be 'Why should I use it over eg Nginx?' It would be helpful to have some direct comparison to other servers on the landing page.
EDIT: Ok, there is a link to some odd benchmarks and it includes performance comparisons to Nginx and others which are not understandable (Nginx 141 req/s and Nxweb 200 / 121 req/s while it's not clear when 200 and when 121); moreover they compare it to Mongoose which is an ORM/ODM
- sanxiyn 11y agoMongoose is a web server. See https://github.com/cesanta/mongoose https://github.com/cesanta/mongoose. It's obviously not https://github.com/Automattic/mongoose https://github.com/Automattic/mongoose.
- chrissnell 11y agoThose benchmarks are well and great but with HTTP/2 support in nginx, do they even matter? I'm reasonably certain that nginx will out-perform for the average client in real-world, TLS-enabled testing.
- rand1012 11y agoI want to use it on Raspberry Pi
- rdw 11y agoTook me a bit of searching to figure out the 200/121 numbers. The answer: "first measurement is for inprocess handler, second is for inworker handler"
- westi 11y agoThe benchmarks also appear to compare to nginx v1.1.12 which is from 2011, not the latest nginx
- bobwaycott 11y agoI only spent a minute on the benchmark page, but it says quite clearly the reqs/s are given in the thousands, and explains each test, as well as the conditions. However, that doesn't change the why question at all. Except it could be neat to not need the complication of setting up nginx with uwsgi for those who like the built-in Python/WSGI support.