Christian Wirth

Results 102 comments of Christian Wirth

> @wirthi thanks for quick reply , for .close() i have to create context for every call , and it will give bad performance, that means we cannot cached the...

Hi, no, unless you are on GraalVM 19. You should be on GraalVM 21.x., if not GraalVM 22.x. The comment was a workaround for GraalVM 19 specifically. > Today i...

Hi, yes, that is possible. You need to make sure you correctly https://www.graalvm.org/truffle/javadoc/org/graalvm/polyglot/Context.html#enter-- and https://www.graalvm.org/truffle/javadoc/org/graalvm/polyglot/Context.html#leave-- when switching threads. -- Christian

Hi @nksaini83 I don't know anything on the details of the memory-related problem on your side. My comment was that **if you never close a Context**, as you stated in...

Hi, I think the problem here is in the ECMAScript specification (and we just play by those rules). https://www.ecma-international.org/ecma-262/10.0/index.html#sec-array.prototype.foreach states that > callbackfn should be a function that accepts three...

You are missing to put the name "Response" into the global scope. Have a look at `JSRealm.setupGlobals`. This way, there are builtins for `Response` but JavaScript does not know what...

Hi @weixingsun thanks for your question. I am trying to understand what your benchmark script (`test_graal.sh`) is doing. It obviously does something, and terminates after ~130 seconds on my machine,...

Hi @EdwardDrapkin thanks for sharing your benchmark. I am no expert on webpack - I guess the `modules/pp3/` is the actual thing you pack? You didn't provide that in your...

Hi @hc-codersatlas we are currently working on significant startup improvements by AOT-compiling larger parts of the Node.js codebase. This is a significant engineering effort though, so it takes a while....

Hi @4ntoine thanks for your code. I confirm we can execute it and measure performance. Your benchmark does not consider [warm-up](https://en.wikipedia.org/wiki/Just-in-time_compilation#Startup_delay_and_optimizations). To mitigate that, you can put a loop around...