V8PROJECT.BLOGSPOT.COM

V8 JavaScript Engine: Getting Garbage Collection for Free

http://www.v8project.blogspot.com/2015/08/getting-garbage-collection-for-free.html

Friday, August 7, 2015. Getting Garbage Collection for Free. Many modern language engines such as Chrome's V8 JavaScript engine dynamically manage memory for running applications so that developers don't need to worry about it themselves. The engine periodically passes over the memory allocated to the application, determines which data is no longer needed, and clears it out to free up room. This process is known as garbage collection. Chrome 41 included a task scheduler for the Blink rendering engine.

V8 JavaScript Engine: Code caching

http://www.v8project.blogspot.com/2015/07/code-caching.html

Monday, July 27, 2015. V8 uses just-in-time compilation. JIT) to execute Javascript code. This means that immediately prior to running a script, it has to be parsed and compiled - which can cause considerable overhead. As we announced recently. Code caching has been available since V8 version 4.2 and not limited to Chrome alone. It is exposed through V8’s API, so that every V8 embedder can take advantage of it. The test case. Used to exercise this feature serves as an example of how to use this API.

V8 JavaScript Engine: Digging into the TurboFan JIT

http://www.v8project.blogspot.com/2015/07/digging-into-turbofan-jit.html

Monday, July 13, 2015. Digging into the TurboFan JIT. Last week we announced. That we've turned on TurboFan for certain types of JavaScript. In this post we wanted to dig deeper into the design of TurboFan. Delivering a new level of performance. We're already seeing some great speedups. With TurboFan, but there's still a ton of work to do. Stay tuned as we enable more optimizations and turn TurboFan on for more types of code! Posted by Ben L. Titzer, Software Engineer and TurboFan Mechanic. Digging into ...

V8 JavaScript Engine: July 2015

http://www.v8project.blogspot.com/2015_07_01_archive.html

Monday, July 27, 2015. V8 uses just-in-time compilation. JIT) to execute Javascript code. This means that immediately prior to running a script, it has to be parsed and compiled - which can cause considerable overhead. As we announced recently. Code caching has been available since V8 version 4.2 and not limited to Chrome alone. It is exposed through V8’s API, so that every V8 embedder can take advantage of it. The test case. Used to exercise this feature serves as an example of how to use this API.

V8 JavaScript Engine: Hello, World!

http://www.v8project.blogspot.com/2015/07/hello-world.html

Friday, July 10, 2015. Welcome to the V8 Developer blog! Historically, the V8 team has published blog posts on the Chromium blog. July 10, 2015 at 9:15 AM. July 10, 2015 at 9:21 AM. Fantastic. Looking forward to this. July 10, 2015 at 9:32 AM. July 10, 2015 at 9:53 AM. Any Twitter we can follow? July 13, 2015 at 10:59 AM. Unfortunately there is currently no V8 Twitter account. July 13, 2015 at 11:59 AM. July 13, 2015 at 12:06 PM. July 10, 2015 at 2:06 PM. July 10, 2015 at 2:40 PM. July 10, 2015 at 5:20 PM.