Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The author of Nginx on why V8 is not suitable for web servers

translate.google.com

Post reply on HN
Print view View original

21–30 of 75 posts

Re: The author of Nginx on why V8 is not suitable for web servers

#21

Post by xer0x »

daeken wrote: post #15
knowtheory wrote: post #12

Earlier quoted context omitted.

I disagree. Where V8 can run is a core part of the deployment surface of node.js, so what server authors think about V8 and it's suitability for integration and deployment very much matter to node.js. Remember, 'does rails scale'? :|

Even if every one of these issues applies to node.js, this article is not "on node.js". The title is incorrect, no matter what.

Agreed. The title is totally trolling for attention.

Nginx and Nodejs are very different. Nodejs was built on V8 from the beginning, while it would have to be grafted into Nginx somehow. Nodejs isn't Chrome but it's willing to pretend that it is - nginx isn't.

Re: The author of Nginx on why V8 is not suitable for web servers

#22

Post by [deleted] »

xer0x wrote: post #21
daeken wrote: post #15

Earlier quoted context omitted.

Even if every one of these issues applies to node.js, this article is not "on node.js". The title is incorrect, no matter what.

Agreed. The title is totally trolling for attention. Nginx and Nodejs are very different. Nodejs was built on V8 from the beginning, while it would have to be grafted into Nginx somehow. Nodejs isn't Chrome but it's willing to pretend that it is - nginx isn't.

[deleted]

Re: The author of Nginx on why V8 is not suitable for web servers

#23

Post by alastairpat »

baguasquirrel wrote: post #2

It's scary what you can do with machine translation these days...

I thought exactly the same thing!

I still remember being able to play a game with one of my friends where we'd translate a sentence to German then back to English and laugh at how mangled it was…

Re: The author of Nginx on why V8 is not suitable for web servers

#25

Post by cagenut »

These only sound like problems if you need to keep it single process. If you break out the javascript interpreter via fastcgi workers just like people do with php on nginx it becomes mostly moot points right? At that point its limited to 500 req/sec/core, but frankly these days that means 4000 req/s, which, hell, I'll take it.

Granted thats assuming you can actually run a fastcgi/v8 setup, I've never looked. I wonder how hard a mod_v8 for apache prefork would be.

Re: The author of Nginx on why V8 is not suitable for web servers

#26

Post by EGreg »

Sysoev brings up a couple good points that affect Node.js .

1) The fact memory allocation might crash the process is a serious problem. Is this still the case?

2) The fact that garbage collection is still stop-the-world may be a problem for server availability. Are we able to call the generational collector from node, or no?

Things that don't involve node:

The ability to create multiple objects in different contexts. Sysoev is thinking of the "scripting" model, like PHP, which is not how Node does things. Node just runs one process to handle thousands of requests, not thousands of processes or threads. There is no need.

Re: The author of Nginx on why V8 is not suitable for web servers

#27

Post by ballard »

Node.js is often used because it is cool, new and easier for front-end developers to develop a functioning backend.

For more traditional uses that want something less hackish, erlang for example, crashes only a single thread not the entire vm. Functional programming languages in general like haskell and erlang are interesting for backend core services.

Re: The author of Nginx on why V8 is not suitable for web servers

#28

Post by ballard »

Node.js is often used because it is cool, new and easier for front-end developers to develop a functioning backend.

For more traditional uses that want something less hackish, erlang for example, crashes only a single thread not the entire vm. Functional programming languages in general like haskell and erlang are interesting for backend core services.

Re: The author of Nginx on why V8 is not suitable for web servers

#29

Post by hanszeir »

xer0x wrote: post #21
daeken wrote: post #15

Earlier quoted context omitted.

Even if every one of these issues applies to node.js, this article is not "on node.js". The title is incorrect, no matter what.

Agreed. The title is totally trolling for attention. Nginx and Nodejs are very different. Nodejs was built on V8 from the beginning, while it would have to be grafted into Nginx somehow. Nodejs isn't Chrome but it's willing to pretend that it is - nginx isn't.

The title is a copy from a Reddit posting. I thought about changing it. Node.js is build on top of V8. It is better to get attention from Node.js experts so that others can get a clearer picture. Updated: Never mind, someone just change the title for me. The original title is "The author of Nginx on node.js and why V8 is not suitable for web servers.".

Re: The author of Nginx on why V8 is not suitable for web servers

#30

Post by argvzero »

xer0x wrote: post #21
daeken wrote: post #15

Earlier quoted context omitted.

Even if every one of these issues applies to node.js, this article is not "on node.js". The title is incorrect, no matter what.

Agreed. The title is totally trolling for attention. Nginx and Nodejs are very different. Nodejs was built on V8 from the beginning, while it would have to be grafted into Nginx somehow. Nodejs isn't Chrome but it's willing to pretend that it is - nginx isn't.

Let me guess. You've never embedded a language VM into another system?
Post reply on HN