On 2015/02/18 11:26:40, Yang wrote:
On 2015/02/18 11:24:18, ulan wrote:
> [+Thomas]
This can be achieved just as easily by using
ResourceConstraints.set_max_available_threads, which is designed for this
use
case. Why do we need an second way to do this?
Right, that is better :)
At the moment the max_available_threads is ignored in GC and platform thread
pool. I uploaded a CL that fixes the GC part:
https://codereview.chromium.org/916103005/
Closing this CL.
https://codereview.chromium.org/938683002/
--
--
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/d/optout.
