<?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/698ca41d993f47519568b06188ed1b1e&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/698ca41d993f47519568b06188ed1b1e-db99a122ea9841c7.gif</thumbnail_url><duration>185.392</duration><title>Optimizing Database Queries for Better Performance 🚀</title><description>In this video, I discuss the performance issues I encountered with my content queries, which were too slow due to inefficient function calls. I implemented a new approach using distinct queries and outer joins, which significantly improved execution time by utilizing indices effectively. The previous method resulted in a prohibitive sequential scan, while the new method shows a drastic reduction in execution time to milliseconds, although the database was empty during testing. I encourage you to review the changes I&apos;ve made to the resource access for my contents, documents, concepts, and file references, as they should enhance our overall efficiency.</description></oembed>