blog

Personal blog
git clone git://git.laack.co/blog.git
Log | Files | Refs

commit 26934f6962daa393b59ddd517b1c48f372ae3a42
parent 4d5f6ac5e6ed6cea4217fa027caf54d2558ea85e
Author: Andrew Laack <andrew@laack.co>
Date:   Wed,  7 Oct 2026 09:50:55 -0500

Messing with format of svgs

Co-authored-by: Vim

Diffstat:
Mposts/entries/pygame-vs-raylib.md | 5+++--
Mposts/gemini/feed.xml | 8+++-----
Mposts/site/feed.xml | 8+++-----
Mposts/site/pygame-vs-raylib.html | 6++----
4 files changed, 11 insertions(+), 16 deletions(-)

diff --git a/posts/entries/pygame-vs-raylib.md b/posts/entries/pygame-vs-raylib.md @@ -299,11 +299,12 @@ Based on this, we see the first frame times are on par with what we actually saw ##### PyGame Flamegraph -<object data="images/pygame-flamegraph.svg" type="image/svg+xml" width="100%"></object> +<img src="images/pygame-flamegraph.svg" style="max-width:100%; height:auto;"> ##### Raylib Flamegraph -<object data="images/rlib-flamegraph.svg" type="image/svg+xml" width="100%"></object> +<img src="images/rlib-flamegraph.svg" style="max-width:100%; height:auto;"> + We see most of our time is being spent in `EndDrawing()` for Raylib and `pygame.display.update()` for Pygame. After instrumenting these calls we find the following times per invocation: diff --git a/posts/gemini/feed.xml b/posts/gemini/feed.xml @@ -7,7 +7,7 @@ <language>en-us</language> <managingEditor>andrew@laack.co</managingEditor> <webMaster>andrew@laack.co</webMaster> -<lastBuildDate>Tue, 06 Oct 2026 21:28:45 -0500</lastBuildDate> +<lastBuildDate>Wed, 07 Oct 2026 09:50:43 -0500</lastBuildDate> <atom:link href="gemini://blog.laack.co/feed.xml" rel="self" type="application/rss+xml"/> <item> <title><![CDATA[PyGame vs. Raylib]]></title> @@ -308,11 +308,9 @@ pygame.draw.line(display, WHITE, (self.v1.x,self.v1.y), (self.v2.x,self.v2.y), L </table> <p>Based on this, we see the first frame times are on par with what we actually saw in our benchmarking, but the subsequent frame draw times are orders of magnitude faster than what we benchmarked, and since most frames are subsequent frames, they are severely impacting performance. Let’s see if we can figure out why this disparity exists.</p> <h5 id="pygame-flamegraph">PyGame Flamegraph</h5> -<object data="images/pygame-flamegraph.svg" type="image/svg+xml" width="100%"> -</object> +<p><img src="images/pygame-flamegraph.svg" style="max-width:100%; height:auto;"></p> <h5 id="raylib-flamegraph">Raylib Flamegraph</h5> -<object data="images/rlib-flamegraph.svg" type="image/svg+xml" width="100%"> -</object> +<p><img src="images/rlib-flamegraph.svg" style="max-width:100%; height:auto;"></p> <p>We see most of our time is being spent in <code>EndDrawing()</code> for Raylib and <code>pygame.display.update()</code> for Pygame. After instrumenting these calls we find the following times per invocation:</p> <table> <thead> diff --git a/posts/site/feed.xml b/posts/site/feed.xml @@ -7,7 +7,7 @@ <language>en-us</language> <managingEditor>andrew@laack.co</managingEditor> <webMaster>andrew@laack.co</webMaster> -<lastBuildDate>Tue, 06 Oct 2026 21:28:45 -0500</lastBuildDate> +<lastBuildDate>Wed, 07 Oct 2026 09:50:43 -0500</lastBuildDate> <atom:link href="https://blog.laack.co/feed.xml" rel="self" type="application/rss+xml"/> <item> <title><![CDATA[PyGame vs. Raylib]]></title> @@ -308,11 +308,9 @@ pygame.draw.line(display, WHITE, (self.v1.x,self.v1.y), (self.v2.x,self.v2.y), L </table> <p>Based on this, we see the first frame times are on par with what we actually saw in our benchmarking, but the subsequent frame draw times are orders of magnitude faster than what we benchmarked, and since most frames are subsequent frames, they are severely impacting performance. Let’s see if we can figure out why this disparity exists.</p> <h5 id="pygame-flamegraph">PyGame Flamegraph</h5> -<object data="images/pygame-flamegraph.svg" type="image/svg+xml" width="100%"> -</object> +<p><img src="images/pygame-flamegraph.svg" style="max-width:100%; height:auto;"></p> <h5 id="raylib-flamegraph">Raylib Flamegraph</h5> -<object data="images/rlib-flamegraph.svg" type="image/svg+xml" width="100%"> -</object> +<p><img src="images/rlib-flamegraph.svg" style="max-width:100%; height:auto;"></p> <p>We see most of our time is being spent in <code>EndDrawing()</code> for Raylib and <code>pygame.display.update()</code> for Pygame. After instrumenting these calls we find the following times per invocation:</p> <table> <thead> diff --git a/posts/site/pygame-vs-raylib.html b/posts/site/pygame-vs-raylib.html @@ -397,11 +397,9 @@ </table> <p>Based on this, we see the first frame times are on par with what we actually saw in our benchmarking, but the subsequent frame draw times are orders of magnitude faster than what we benchmarked, and since most frames are subsequent frames, they are severely impacting performance. Let’s see if we can figure out why this disparity exists.</p> <h5 id="pygame-flamegraph">PyGame Flamegraph</h5> -<object data="images/pygame-flamegraph.svg" type="image/svg+xml" width="100%"> -</object> +<p><img src="images/pygame-flamegraph.svg" style="max-width:100%; height:auto;"></p> <h5 id="raylib-flamegraph">Raylib Flamegraph</h5> -<object data="images/rlib-flamegraph.svg" type="image/svg+xml" width="100%"> -</object> +<p><img src="images/rlib-flamegraph.svg" style="max-width:100%; height:auto;"></p> <p>We see most of our time is being spent in <code>EndDrawing()</code> for Raylib and <code>pygame.display.update()</code> for Pygame. After instrumenting these calls we find the following times per invocation:</p> <table> <thead>