<?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/8adb7ccc61e94d24854305ea582c03f4&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/8adb7ccc61e94d24854305ea582c03f4-7e50f726fdd52fe6.gif</thumbnail_url><duration>868.167</duration><title>Day 16 - Crash-n-Clash - 05 Edit</title><description>In this video, I walk you through the process of refining our proof-of-concept by optimizing our filters for better performance, especially on larger projects with thousands of elements. I emphasize the importance of applying quick filters before slow filters to improve efficiency, demonstrating how to implement a bounding box intersects filter. We also enhance the report format to make it more user-friendly by including wall names alongside IDs. I encourage you to test the updated code and provide feedback on its performance. Lastly, I plan to conduct stress tests to ensure everything runs smoothly.</description></oembed>