<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/90b7707271b04ed09f61202b57202cd7&quot; frameborder=&quot;0&quot; width=&quot;1730&quot; height=&quot;1297&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1297</height><width>1730</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1297</thumbnail_height><thumbnail_width>1730</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/90b7707271b04ed09f61202b57202cd7-27482befb6539d0f.gif</thumbnail_url><duration>394.452</duration><title>[Feature Tutorial] TraceDiffs: A New Way to Analyze Code Changes! 🚀</title><description>Hey everyone, I’m excited to introduce our newest feature, TraceDiffs, which allows you to compare two traces much like GitDiff does for code. I demonstrated this by selecting a base trace from version 0.12.0 VLLM and comparing it with version 0.13, running the same workload. Once you select your traces and run TraceDiff, you can view the differences in the Perfetov viewer, where the top streams correspond to the base trace. I encourage you to try this out and explore how individual kernels and timelines have changed. Let me know what you think!</description></oembed>