Hi Jules,
Thanks for your responses.
So you're timing only the execution of very small scripts that are generated on the fly and don't access host resources. If that's correct, then it's likely that what you're measuring is mostly the overhead of invoking V8 via ClearScript, which is relatively high because of the transition from managed to native code. A 100% managed interpreter such as Jint might be a better fit for you.
If you choose to stick with ClearScript and would like to improve your overall request processing throughput, consider using a pool of V8 engine instances instead of creating a new one for each request. Also, we strongly recommend that you dispose V8 instances explicitly; each instance reserves a very large block of address space, so it's important not to let them pile up until garbage collection takes place.
Good luck!
Thanks for your responses.
So you're timing only the execution of very small scripts that are generated on the fly and don't access host resources. If that's correct, then it's likely that what you're measuring is mostly the overhead of invoking V8 via ClearScript, which is relatively high because of the transition from managed to native code. A 100% managed interpreter such as Jint might be a better fit for you.
If you choose to stick with ClearScript and would like to improve your overall request processing throughput, consider using a pool of V8 engine instances instead of creating a new one for each request. Also, we strongly recommend that you dispose V8 instances explicitly; each instance reserves a very large block of address space, so it's important not to let them pile up until garbage collection takes place.
Good luck!