<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>partitioning on chrismoos</title>
    <link>/tags/partitioning/</link>
    <description>Recent content in partitioning on chrismoos</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020 Chris Moos</copyright>
    <lastBuildDate>Sun, 31 Jan 2010 12:43:58 +0000</lastBuildDate><atom:link href="/tags/partitioning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MySQL and partitioning tables with millions of rows</title>
      <link>/2010/01/31/mysql-partitioning-tables-with-millions-of-rows/</link>
      <pubDate>Sun, 31 Jan 2010 12:43:58 +0000</pubDate>
      
      <guid>/2010/01/31/mysql-partitioning-tables-with-millions-of-rows/</guid>
      <description>The Problem I&#39;ve been running a mobile GPS tracking service, MoosTrax (formerly BlackBerry Tracker), for a few years and have encountered a large amount of data in the process.
A user&#39;s phone sends its location to the server and it is stored in a MySQL database. Each &#34;location&#34; entry is stored as a single row in a table.
Right now there are approximately 12 million rows in the location table, and things are getting slow now, as a full table scan can take ~3-4 minutes on my limited hardware.</description>
    </item>
    
  </channel>
</rss>
