<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: MonetDB for Everybody</title>
	<link>http://www.lshift.net/blog/2005/09/26/monetdb-for-everybody</link>
	<description>What happens at LShift</description>
	<pubDate>Wed, 08 Oct 2008 03:35:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: matthias</title>
		<link>http://www.lshift.net/blog/2005/09/26/monetdb-for-everybody#comment-389</link>
		<pubDate>Wed, 12 Apr 2006 07:48:57 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2005/09/26/monetdb-for-everybody#comment-389</guid>
					<description>&lt;p&gt;I finally got the chance to take a closer look at MonetDB - building it, installing it, and running through some performance tests.&lt;/p&gt;

&lt;p&gt;On one of our projects we have been plagued by MySQL's and other databases inability to efficiently execute a variety of &lt;code&gt;count(*)&lt;/code&gt; queries on a table with 4 million rows. For example, MySQL will take 40 seconds to run &lt;code&gt;select count(*) from table&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;In MonetDB the same queries return results instantly. And that's without configuring any keys or indices! I am not sure it is actually avoiding the counting in those queries - it may just be able to count very very fast.&lt;/p&gt;

&lt;p&gt;However, MonetDB's SQL implementation has some gaps, though it aims to conform to SQL'99 and '03, unlike MySQL's SQL'92. I also found the documentation to be in quite bad shape - there's a fair amount of it but it is really badly organized and presented. So, for the time being at least, MonetDB is still to immature to use in production systems.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I finally got the chance to take a closer look at MonetDB - building it, installing it, and running through some performance tests.</p>
<p>On one of our projects we have been plagued by MySQL&#8217;s and other databases inability to efficiently execute a variety of <code>count(*)</code> queries on a table with 4 million rows. For example, MySQL will take 40 seconds to run <code>select count(*) from table</code>.</p>
<p>In MonetDB the same queries return results instantly. And that&#8217;s without configuring any keys or indices! I am not sure it is actually avoiding the counting in those queries - it may just be able to count very very fast.</p>
<p>However, MonetDB&#8217;s SQL implementation has some gaps, though it aims to conform to SQL&#8217;99 and &#8216;03, unlike MySQL&#8217;s SQL&#8217;92. I also found the documentation to be in quite bad shape - there&#8217;s a fair amount of it but it is really badly organized and presented. So, for the time being at least, MonetDB is still to immature to use in production systems.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
