On Fri, Sep 20, 2013 at 1:25 PM, <[email protected]> wrote: > [...] then I think it would be best to have some clear entry point > to initialize V8 where it's explicit to the embedder that they should be > setting > these constraints. This is difficult right now due to the default isolate, > and I > don't think having this in SetResourceConstraints would work since it is > easy to > call this too late (after the heap has been set up), and I don't think many > embedders even call it (Chrome doesn't for the main thread, and only uses > it to > set the stack size for worker threads). Any thoughts on this? >
-1 on new entry points. SetResourceConstraints is the way to go, finding the right place to call it from Chrome shouldn't be an issue. In the not-too-far future this should be an optional argument for Isolate creation, anyway, and I don't want to design something now which will be dead soon just because the current API is so fragile. Apart from that, I don't have any strong opinion on the topic itself, apart from the fact that v8 should never decide on its own how much memory it should use at most. We simply don't know how much the embedder/user wants us to use, even if we have e.g. a 64GB machine the app using v8 might want to limit it to let's say 2GB because a lot of app instances are spawned. We just don't know the scenario from within v8, so this should be controlled somehow from the outside, and this is the reason why all runtimes I know of have some controllable limits. -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
