trace-chrome is a command line tool I wrote to make it easy to capture a Chromium trace from a remote device.
cc @igalia.com @chromium.social #webperf
trace-chrome is a command line tool I wrote to make it easy to capture a Chromium trace from a remote device.
cc @igalia.com @chromium.social #webperf
This is the topic of my new post: blogs.igalia.com/dape/2025/02...
cc @igalia.com @chromium.social
This is the topic of my new post: blogs.igalia.com/dape/2025/02...
cc @igalia.com @chromium.social
This deep-dive talk by @jason-williams.co.uk & @pcwilliams.net reveals what that looks like in terms of Chromium embedding.
It explains how we keep it blazing fast, including by adding a new Web Perf API: Container Timing 🔥
dbezhetskov.dev/multi-sandbo...
dbezhetskov.dev/multi-sandbo...
www.igalia.com/2024/12/20/C...
www.igalia.com/2024/12/20/C...
I will be hosting a breakout session about Linux #Chromium running in low memory devices, and delivering a lightning talk about the work I have been involved to improve the #V8 support for native stack walking profiling.
See you at BlinkOn! cc @igalia.bsky.social
I will be hosting a breakout session about Linux #Chromium running in low memory devices, and delivering a lightning talk about the work I have been involved to improve the #V8 support for native stack walking profiling.
See you at BlinkOn! cc @igalia.bsky.social
blogs.igalia.com/dape/2024/09...
Continuing the series, this post dives into a crucial aspect: keeping track of the upstream #Chromium repositories changes.
cc @igalia.bsky.social
blogs.igalia.com/dape/2024/09...
Continuing the series, this post dives into a crucial aspect: keeping track of the upstream #Chromium repositories changes.
cc @igalia.bsky.social
This time I write about why projects use Chromium, and why a downstream may be needed. This is the first post of a series about the challenges of maintaining a downstream of Chromium.
cc @igalia.bsky.social
This time I write about why projects use Chromium, and why a downstream may be needed. This is the first post of a series about the challenges of maintaining a downstream of Chromium.
cc @igalia.bsky.social
When profiling Javascript CPU usage, JIT-compiled code needs instrumentation. Unfortunately, in V8 it is disabled by default because of its overhead. I ran benchmarks to measure that. cc @igalia.bsky.social
When profiling Javascript CPU usage, JIT-compiled code needs instrumentation. Unfortunately, in V8 it is disabled by default because of its overhead. I ran benchmarks to measure that. cc @igalia.bsky.social
Main highlights from web stack side: It is now based on Chromium m108. And we now use LLVM Clang and libc++, instead of libstdc++ and GCC. That way we align better with upstream, far more tested with this toolchain.
www.webosose.org/blog/2023/11...
Main highlights from web stack side: It is now based on Chromium m108. And we now use LLVM Clang and libc++, instead of libstdc++ and GCC. That way we align better with upstream, far more tested with this toolchain.
www.webosose.org/blog/2023/11...
Though Chromium official toolchains for Linux are based on LLVM Clang and libc++, GNU toolchain is supported as a community effort. In the post I write about current status (working!).
Thanks to all contributors! cc @igalia.bsky.social
blogs.igalia.com/dape/2023/11...
Though Chromium official toolchains for Linux are based on LLVM Clang and libc++, GNU toolchain is supported as a community effort. In the post I write about current status (working!).
Thanks to all contributors! cc @igalia.bsky.social
blogs.igalia.com/dape/2023/11...