<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on terrakok</title><link>https://terrablog.pages.dev/tags/performance/</link><description>Recent content in Performance on terrakok</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://terrablog.pages.dev/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Profiling a Compose Multiplatform app in the browser</title><link>https://terrablog.pages.dev/blog/profiling-compose-multiplatform-app-in-browser/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://terrablog.pages.dev/blog/profiling-compose-multiplatform-app-in-browser/</guid><description>&lt;h2 id="youve-noticed-a-performance-problem" class="heading-with-anchor"&gt;&#10; You&amp;rsquo;ve noticed a performance problem&#10; &lt;a class="heading-anchor" href="#youve-noticed-a-performance-problem" data-copy-heading-link data-heading-title="You’ve noticed a performance problem" title="Copy a link to this heading" aria-label="Copy a link to heading: You’ve noticed a performance problem"&gt;#&lt;/a&gt;&#10;&lt;/h2&gt;&#10;&lt;h3 id="first-steps" class="heading-with-anchor"&gt;&#10; First steps&#10; &lt;a class="heading-anchor" href="#first-steps" data-copy-heading-link data-heading-title="First steps" title="Copy a link to this heading" aria-label="Copy a link to heading: First steps"&gt;#&lt;/a&gt;&#10;&lt;/h3&gt;&#10;&lt;p&gt;I hope everyone already knows that to check the performance of a Compose app, you need to run it in &lt;strong&gt;release mode&lt;/strong&gt;. Development mode is designed for quick iterations and skips a lot of build-time optimizations.&#10;So first of all, if you see that the app is lagging and dropping frames, make sure you&amp;rsquo;re &lt;strong&gt;not&lt;/strong&gt; running it in development mode.&lt;br&gt;&#10;If the problems are still there even in a release build, then, of course, you need to figure out what went wrong.&#10;Don&amp;rsquo;t jump straight into the &lt;em&gt;hardcore&lt;/em&gt; stuff! First, just take a sensible look at what&amp;rsquo;s happening inside the app.&#10;Nobody knows your codebase better than you do. Maybe, by accident, you&amp;rsquo;re decoding a large JSON file on the UI thread. Or maybe you&amp;rsquo;re making a database query. And so on. 😉&lt;/p&gt;</description></item></channel></rss>