Live data from Hacker News

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

translate.google.com

51–60 of 75 posts

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

#52

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

Technical texts like this are relatively easy to get right. English is not my native language and when I was young I could read computer related stuff, but had trouble understanding, for example Harry Potter. If Google has an example of such a text, they can learn all the translations for all the technical terms from that data. However, a news article is much more difficult because they often have lot's of metaphors, etc. If you try to translate those, you get a lot of halve finished sentences and stuff like that.

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

#53

Speaking only for myself as ever: Handling out of memory errors is a hard problem. At the point when you can't allocate more memory you are busted in most languages. For example in C a slightly deeper function call depth can cause the stack to expand at any point. If that point coincides with you running out of memory then you are busted. No program can keep running with a broken stack. If V8 were capable of recoveri…

You're being too clever - if you run out of memory, throw away the request and all associated resources and return "500: Internal server error". There are lots of reasons why this isn't perfect (if the OS overcommits memory, like Linux (typically?) does, it will have to kill you to avoid running out; if you need to use swap you're too slow to be useful; etc), but it's not impossible.

node.js (one process for many requests) is a different model than the author is considering; no matter its (dis)advantages, integrating it into the server is not nearly as advantageous as for a process-per-request model (like mod_php).

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

#54
post #47

IIRC, on Linux at least the memory allocation thing is moot. If your process runs out of memory, it dies anyway. You can't catch "malloc says no" because malloc never says no. It either says yes or blows your process's brains out.

"malloc never says no" malloc says no if you set a ulimit in your shell. I do this on the desktop to stop myself from shooting myself in the foot. (Recent kernels also let you turn off the overcommitting behavior.)

Recent is 2.6.11+ which is 6 years old.

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

#57
post #50

in russian : Почему Google V8 пока не подходит для встраивания в серверы in english : Why is Google V8 is not suitable for integration into servers. There is a word "integration" that the author of the post forgot to put in.

Почему Google V8 пока не подходит для встраивания в серверы in english :

Why is Google V8 is not yet suitable for integration into servers.

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

#59
post #20
post #18

Earlier quoted context omitted.

It likely was not completely translated by machine. Google Translate lets anyone reading the translation edit it to fix errors. Highlight some text and notice the link that appears allowing you to "Contribute a better translation" for that particular passage.

It's more likely that it only helps train Google Translate, and doesn't actually apply any changes directly to the translated text. Otherwise vandalism would be way too easy.

Right. I noticed a small translation error in the first paragraph. The Russian word "машина" - in the paraphrased Henry Ford quote - is translated as machine, but in the context of the sentence should be translated as "car."

When I corrected it, the old one was left in place.

Post reply on HN