<?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 Oxymoronical</title>
    <link>https://www.oxymoronical.com/blog/tag/performance/</link>
    <description>Recent content in performance on Oxymoronical</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 27 Jan 2016 12:35:25 +0000</lastBuildDate>
    <atom:link href="https://www.oxymoronical.com/blog/tag/performance/feed/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Improving the performance of the add-ons manager with asynchronous file I/O</title>
      <link>https://www.oxymoronical.com/blog/2016/01/Improving-the-performance-of-the-add-ons-manager-with-asynchronous-file-IO/</link>
      <pubDate>Wed, 27 Jan 2016 12:35:25 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2016/01/Improving-the-performance-of-the-add-ons-manager-with-asynchronous-file-IO/</guid>
      <description>&lt;p&gt;The add-ons manager has a dirty secret. It uses an awful lot of synchronous file I/O. This is the kind of I/O that blocks the main thread and can cause Firefox to be janky. I’m told that that is a technical term. Asynchronous file I/O is much nicer, it means you can let the rest of the app continue to function while you wait for the I/O operation to complete. I rewrote much of the current code from scratch for Firefox 4.0 and even back then we were trying to switch to asynchronous file I/O wherever possible. But still I used mostly synchronous file I/O.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zooming along, hopefully as fast as before</title>
      <link>https://www.oxymoronical.com/blog/2009/01/Zooming-along-hopefully-as-fast-as-before/</link>
      <pubDate>Wed, 14 Jan 2009 19:43:14 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2009/01/Zooming-along-hopefully-as-fast-as-before/</guid>
      <description>&lt;p&gt;I’ve just landed a fix to &lt;a href=&#34;https://bugzilla.mozilla.org/show_bug.cgi?id=386835&#34;&gt;a bug&lt;/a&gt; that has irritated me ever since page zoom started getting remembered for sites. It fixes a real problem you find if you both use zoom a fair bit, and load pages in background tabs. When you finally decide to look at that tab there is this little pause (or long pause if the page is large) and sometimes a visual jump as it re-zooms the content. It also changes where the page is scrolled to which is very irritating if you have just clicked a link to a specific line in some source code for example.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How extensions can slow down Firefox (my dirty little secret)</title>
      <link>https://www.oxymoronical.com/blog/2008/10/How-extensions-can-slow-down-Firefox-my-dirty-little-secret/</link>
      <pubDate>Mon, 06 Oct 2008 11:21:24 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2008/10/How-extensions-can-slow-down-Firefox-my-dirty-little-secret/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.oxymoronical.com/web/firefox/TabSidebar&#34;&gt;Tab Sidebar&lt;/a&gt; is probably my favourite extension that I’ve created. It is certainly the most polished, thanks mostly to other people pushing me to make it so. For those that haven’t used it it creates a thumbnail preview of all of your tabs in the sidebar. The thumbnails automatically update whenever the page changes, even things like popup menus generally show up. This automatic updating comes at a cost though.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
