Nxweb – Fast and Lightweight Web Server

Post by paulddraper » Sun, Feb 28, 2016, 3:03 AM UTC

ktRolster wrote: post #63

geocar wrote: post #16

Earlier quoted context omitted.

Specifically it's garbage collection. e.g. node.js has no problem getting 20k/sec per core, but a stall at the wrong time kills every pipelined HTTP request that follows (until you tear down the connection and restart it).

Worth also mentioning that ad servers tend to have massive RAM requirements (again, for speed). GC in a 30GB JVM can take 10 minutes. To handle it, companies mark the boxes as 'inoperable' when they are in GC mode and remove them from the cluster until thy are ready to return. All of this is motivation to rewrite everything in C.

Post by evthewolf » Sun, Feb 28, 2016, 12:32 PM UTC

sanxiyn wrote: post #10

glossyscr wrote: post #7

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); mo…

Mongoose is a web server. See https://github.com/cesanta/mongoose . It's obviously not https://github.com/Automattic/mongoose .

Post by goldenkey » Sat, Mar 05, 2016, 3:10 PM UTC

pjmlp wrote: post #45

goldenkey wrote: post #21

Earlier quoted context omitted.

Java is garbage unless you specific 20 -D options to bend it to your will.

I could say the same thing of compiler optimisation flags.