<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">

<channel>
  <title>Sturnus Performance</title>
  <link>http://www.sturnus.co.uk/performance/</link>
  <description>Practical information for anyone who wants to develop fast, efficient software</description>
  <language>en</language>

  <item>
    <title>Featured in Dr Dobb's Journal: Improving Database OLTP Throughput via Batching</title>
    <link>http://drdobbs.com/web-development/229218866</link>
    <description>This month I'm delighted to be featured in the prestigious Dr Dobb's Journal. Check out my article on how to ditch multi-threading and connection pools, and improve your database OLTP throughput by batching queries.
    </description>
  </item>

  <item>
    <title>Testing Character Types</title>
    <link>http://www.sturnus.co.uk/performance/2010-09/testing-character-types/</link>
    <description>Look-up tables are an ideal way of testing whether characters are of a particular type, and are commonly used in C for functions such as isupper, isdigit etc. You can also use them for your own custom classification tests.
    </description>
  </item>

  <item>
    <title>Index Troubleshooting: Why Is My Index Not Used?</title>
    <link>http://www.sturnus.co.uk/performance/2010-09/why-is-my-index-not-used/</link>
    <description>You're very pleased with yourself: you've created your index, and are feeling supremely confident that your query is now going to run much faster. But something's wrong. The query is still slow, and your index is not being used at all. What's going on? It can be confusing, frustrating, and sometimes downright annoying, but there are plenty of simple reasons why your bright shiny index gets ignored.
    </description>
  </item>

  <item>
    <title>Introduction To Look-up Tables</title>
    <link>http://www.sturnus.co.uk/performance/2010-09/introduction-to-lookup-tables/</link>
    <description>Look-up tables are a common performance tool that allows us to use values or results that have been calculated ahead of time, i.e. in advance of when they are needed. This introduction discusses why and how you might use a look-up table.
    </description>
  </item>

  <item>
    <title>Indexes Are All Around (Part 2)</title>
    <link>http://www.sturnus.co.uk/performance/2010-09/indexes-are-all-around-part-2/</link>
    <description>The second part of this introduction to relational database indexing looks at the most common type of index that we use.
    </description>
  </item>

  <item>
    <title>Indexes Are All Around (Part 1)</title>
    <link>http://www.sturnus.co.uk/performance/2010-08/indexes-are-all-around-part-1/</link>
    <description>As an introduction to the wonderful world of relational database indexing, I take a look at some common real-life indexes that we use every day.
    </description>
  </item>

  <item>
    <title>sybtop</title>
    <link>http://www.sturnus.co.uk/performance/2008-10/sybtop/</link>
    <description>For those of you who prefer the good old-fashioned command line, rather than all that fancy graphical user interface stuff, here is a handy script that provides a "top"-like display of blocked, blocking, and running processes on a Sybase Adaptive Server Enterprise (ASE) database server.
    </description>
  </item>

  <item>
    <title>Worst Performance Mistakes</title>
    <link>http://www.sturnus.co.uk/performance/2008-09/worst-performance-mistakes/</link>
    <description>I've come across some howlers in my time. So I thought it only fair to share some of these with you for your entertainment. Names have been witheld to protect the guilty.
    </description>
  </item>

  <item>
    <title>The Curse Of The Name-Value Pair</title>
    <link>http://www.sturnus.co.uk/performance/2008-07/the-curse-of-the-name-value-pair/</link>
    <description>When it comes to storing objects in a relational database, one of the worst performance decisions that can be made is to use name-value pairs. In this article I give you a couple of techniques for avoiding them, as well as some ways of improving performance if you insist on using them anyway.
    </description>
  </item>

  <item>
    <title>The Dreaded "Scalable" Word</title>
    <link>http://www.sturnus.co.uk/performance/2008-07/the-dreaded-scalable-word/</link>
    <description>Find out why I hate it when people use the word "scalable", what it actually means, and why, ultimately, it may not be what they want.
    </description>
  </item>

</channel>

</rss>

