<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>jodal.dev - performance</title>
    <subtitle>Personal blog of Stein Magnus Jodal</subtitle>
    <link rel="self" type="application/atom+xml" href="https://jodal.dev/tags/performance/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://jodal.dev"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2019-05-07T00:00:00+00:00</updated>
    <id>https://jodal.dev/tags/performance/atom.xml</id>
    <entry xml:lang="en">
        <title>Pykka 2.0 released with better ergonomics and performance improvements</title>
        <published>2019-05-07T00:00:00+00:00</published>
        <updated>2019-05-07T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2019/05/07/pykka-2.0/"/>
        <id>https://jodal.dev/2019/05/07/pykka-2.0/</id>
        
        <summary type="html">&lt;p&gt;I’ve finally released &lt;a rel=&quot;external&quot; href=&quot;https://pykka.readthedocs.io/&quot;&gt;Pykka&lt;/a&gt; 2.0, the
first major update to Pykka in almost six years.&lt;/p&gt;
&lt;p&gt;Pykka is a Python implementation of the actor model. The actor model
introduces some simple rules to control the sharing of state and cooperation
between execution units, which makes it easier to build concurrent
applications.&lt;/p&gt;
&lt;p&gt;Pykka 2.0 is a major release because it is backwards incompatible in several
minor ways. However, the backwards incompatible changes should only affect
quite narrow use cases.
Mopidy and its extensions,
which is the largest open source ecosystem I know of that uses Pykka,
runs unmodified on Pykka 2.0.&lt;/p&gt;
&lt;p&gt;In this blog post I’ll go through some of the more important improvements in
2.0.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Speeding up a Django web site without touching the code</title>
        <published>2011-10-19T00:00:00+00:00</published>
        <updated>2011-10-19T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2011/10/19/speeding-up-a-django-web-site-without-touching-the-code/"/>
        <id>https://jodal.dev/2011/10/19/speeding-up-a-django-web-site-without-touching-the-code/</id>
        
        <summary type="html">&lt;p&gt;I’ve recently been tweaking my server setup for a Django 1.3 web site with the
goal of making it a bit faster. Of course, there is a lot of speed to gain by
improving e.g. the number of database queries needed to render a web page, but
the server setup also has an effect on the web site performance. This is a log
of my findings.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Traversable attributes in Pykka</title>
        <published>2011-10-06T00:00:00+00:00</published>
        <updated>2011-10-06T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2011/10/06/traversable-attributes-in-pykka/"/>
        <id>https://jodal.dev/2011/10/06/traversable-attributes-in-pykka/</id>
        
        <summary type="html">&lt;p&gt;In &lt;a rel=&quot;external&quot; href=&quot;https://pykka.readthedocs.io/&quot;&gt;Pykka&lt;/a&gt; 0.13–which was released almost two
weeks ago–traversing the attributes of an actor is about 8.3 times faster than
it used to be. To paraphrase Apple: “8.3X faster. That’s amazing!” &lt;em&gt;(Update:
This was written a couple of hours before the news of Jobs’ passing arrived.
May he continue to inspire us.)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;So, what is “traversable attributes”? Let’s take a few steps back.&lt;/p&gt;</summary>
        
    </entry>
</feed>
