FYI: Nginx creator comments on Google V8 shortcomings (maybe related to NodeJS too)

[pcdinh]

Here is the link:

http://translate.google.ru/translate?js=y&prev=_t&hl=ru&ie=UTF-8&layout=1&eotf=1&u=http://sysoev.ru/prog/v8.html&sl=ru&tl=en

[Ivan Boldyrev]

On Wed, Feb 24, 2010 at 11:25 PM, pcdinh <pcd...@gmail.com> wrote:

Here is the link:

http://translate.google.ru/translate?js=y&prev=_t&hl=ru&ie=UTF-8&layout=1&eotf=1&u=http://sysoev.ru/prog/v8.html&sl=ru&tl=en

This is not related to node.js, as a main complain is a long context creation time.  But node.js uses single context created on startup.

But memory overflow handling is a problem indeed.

--
Ivan Boldyrev

[Joran Greef]

Re: "In principle, nothing wrong with using a separate context for
each query there, if not the time to create the context - 2
milliseconds. Of course, when the context is created for each page in
a browser, a user of these 2 milliseconds will not notice, but for the
server, this means that it may set up a second no more than 500
contexts, and therefore can not handle more than 500 queries per
second."

What about creating contexts in advance of the request coming in?

[Ivan Boldyrev]

On Thu, Feb 25, 2010 at 4:51 PM, Joran Greef <joran...@gmail.com> wrote:

What about creating contexts in advance of the request coming in?

Request incoming regulary, without "advance", so pool of contexts will soon be empty.

--
Ivan Boldyrev