<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How is MySQL&#8217;s join performance these days?</title>
	<atom:link href="http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:57:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Quora</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-228568</link>
		<dc:creator>Quora</dc:creator>
		<pubDate>Thu, 23 Jun 2011 09:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-228568</guid>
		<description>&lt;strong&gt;Why do people typically choose PostgreSQL over MySQL?...&lt;/strong&gt;

First off, I believe that whatever you&#039;re doing, you&#039;ll probably be fine using either. That said, I&#039;m generally more frustrated when using MySQL than when using PG. Here&#039;s a sample of the problems I&#039;ve encountered from using both MySQL and PG. I h...</description>
		<content:encoded><![CDATA[<p><strong>Why do people typically choose PostgreSQL over MySQL?&#8230;</strong></p>
<p>First off, I believe that whatever you&#8217;re doing, you&#8217;ll probably be fine using either. That said, I&#8217;m generally more frustrated when using MySQL than when using PG. Here&#8217;s a sample of the problems I&#8217;ve encountered from using both MySQL and PG. I h&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quora</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-228567</link>
		<dc:creator>Quora</dc:creator>
		<pubDate>Thu, 23 Jun 2011 09:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-228567</guid>
		<description>&lt;strong&gt;What are the advantages and disadvantages of using PostgreSQL over MySQL?...&lt;/strong&gt;

First off, I believe that whatever you&#039;re doing, you&#039;ll probably be fine using either. That said, I&#039;m generally more frustrated when using MySQL than when using PG. Here&#039;s a sample of the problems I&#039;ve encountered from using both MySQL and PG. I h...</description>
		<content:encoded><![CDATA[<p><strong>What are the advantages and disadvantages of using PostgreSQL over MySQL?&#8230;</strong></p>
<p>First off, I believe that whatever you&#8217;re doing, you&#8217;ll probably be fine using either. That said, I&#8217;m generally more frustrated when using MySQL than when using PG. Here&#8217;s a sample of the problems I&#8217;ve encountered from using both MySQL and PG. I h&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shamim</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-91268</link>
		<dc:creator>shamim</dc:creator>
		<pubDate>Mon, 21 Jul 2008 18:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-91268</guid>
		<description>Really true. i am satisfied reading your article. 
I can do well. if you get me scholarship. i want to do Msc in software Engineering. i have strong eagernesses,but nobody want help me in this world.</description>
		<content:encoded><![CDATA[<p>Really true. i am satisfied reading your article.<br />
I can do well. if you get me scholarship. i want to do Msc in software Engineering. i have strong eagernesses,but nobody want help me in this world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-90690</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Tue, 15 Jul 2008 15:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-90690</guid>
		<description>And since it&#039;s open source, you can write your own modules even beyond the default cases for doing so. Duh.

Thanks!

CAM</description>
		<content:encoded><![CDATA[<p>And since it&#8217;s open source, you can write your own modules even beyond the default cases for doing so. Duh.</p>
<p>Thanks!</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victoria Eastwood</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-90682</link>
		<dc:creator>Victoria Eastwood</dc:creator>
		<pubDate>Tue, 15 Jul 2008 12:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-90682</guid>
		<description>If you implement only the storage engine interface then you would using the MySQL optimizer. This interface is row oriented and expects indices, which are used among other things to determine the costing.

Since Brighthouse is both column oriented and uses the knowledge grid instead of indices, this type of optimizer is not a good fit for us. So although we have implemented this interface and use it in rare cases, we have written our own optimizer to take advantage of the knowledge grid during query execution.</description>
		<content:encoded><![CDATA[<p>If you implement only the storage engine interface then you would using the MySQL optimizer. This interface is row oriented and expects indices, which are used among other things to determine the costing.</p>
<p>Since Brighthouse is both column oriented and uses the knowledge grid instead of indices, this type of optimizer is not a good fit for us. So although we have implemented this interface and use it in rare cases, we have written our own optimizer to take advantage of the knowledge grid during query execution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-90671</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Mon, 14 Jul 2008 16:35:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-90671</guid>
		<description>Victoria (or anybody),

I probably knew the answer to this, but I&#039;ve forgotten:

When you write your own MySQL storage engine, what happens with the optimizer? Do you do one from scratch? Does MySQL have a basic cost-based optimizer for which you write your own cost functions?

Thanks,

CAM</description>
		<content:encoded><![CDATA[<p>Victoria (or anybody),</p>
<p>I probably knew the answer to this, but I&#8217;ve forgotten:</p>
<p>When you write your own MySQL storage engine, what happens with the optimizer? Do you do one from scratch? Does MySQL have a basic cost-based optimizer for which you write your own cost functions?</p>
<p>Thanks,</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victoria Eastwood</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-90670</link>
		<dc:creator>Victoria Eastwood</dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-90670</guid>
		<description>Some storage engines, including Infobright’s,  implement their own join  algorithms. Infobright implements two join techniques: nested loop and sort-merge. We are also in the process of implementing hash-join. Since we don’t use indices but rather the Knowledge Grid, our implementation of these  techniques is different and the performance dynamic much improved. 

We also implement subqueries using the Knowledge Grid; so we significantly out perform other MySQL storage engines on large datasets. And our clients consistently use joins and subqueries in their queries.</description>
		<content:encoded><![CDATA[<p>Some storage engines, including Infobright’s,  implement their own join  algorithms. Infobright implements two join techniques: nested loop and sort-merge. We are also in the process of implementing hash-join. Since we don’t use indices but rather the Knowledge Grid, our implementation of these  techniques is different and the performance dynamic much improved. </p>
<p>We also implement subqueries using the Knowledge Grid; so we significantly out perform other MySQL storage engines on large datasets. And our clients consistently use joins and subqueries in their queries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Swanhart</title>
		<link>http://www.dbms2.com/2008/07/10/how-is-mysqls-join-performance-these-days/#comment-90476</link>
		<dc:creator>Justin Swanhart</dc:creator>
		<pubDate>Sat, 12 Jul 2008 06:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=461#comment-90476</guid>
		<description>KFDB (the storage engine used in the Kickfire appliances) supports multiple types of joins beyond nested loops, but only for tables backed by the KFDB storage engine.  

Kickfire supports hash joins as well as additional join methods that leverage hardware acceleration.  Kickfire also features accelerated joins to specialized indexes in addition to the performance benefits garnered by vertical column storage.  Join performance may be orders of magnitude faster than other storage engines when using specialized join algorithms.</description>
		<content:encoded><![CDATA[<p>KFDB (the storage engine used in the Kickfire appliances) supports multiple types of joins beyond nested loops, but only for tables backed by the KFDB storage engine.  </p>
<p>Kickfire supports hash joins as well as additional join methods that leverage hardware acceleration.  Kickfire also features accelerated joins to specialized indexes in addition to the performance benefits garnered by vertical column storage.  Join performance may be orders of magnitude faster than other storage engines when using specialized join algorithms.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

