This project is read-only.

Possible issues and performance with multiple engines.


A small number of engines seem to work ok, but some users are reporting that going to 45+ engines seems to crash the app. Will look into this asap.


PhilRykoff wrote Sep 23, 2014 at 7:49 AM

The crash was one point. If you would like to use it as a NodeJS clone, an inherent algorithm of "Engine PreFetching" would be good, too, in order to minimize the time from a user requesting a ressource to the Engine being ready :-)

If you are interested in some source code in this matter, just say the word.

jamesnw wrote Sep 23, 2014 at 7:34 PM

Are you referring to an engine cache/pool?

PhilRykoff wrote Oct 13, 2014 at 7:51 PM

Yeah, like that. No rocket science :-)

jamesnw wrote Oct 16, 2014 at 5:33 PM

Good idea. Instead of disposing the native V8 engine I could just dispose the context and create a new one for the pooled engine later on.