<?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: New OLAP Wikistat benchmark: Introduction and call for feedbacks</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/</link>
	<description>Percona&#039;s MySQL &#38; InnoDB performance and scalability blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-722041</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Tue, 09 Feb 2010 15:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-722041</guid>
		<description>David,

Sure, that makes sense.
Just in current enviroment it may be runaway query,
which will take days to execute for some engines...</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>Sure, that makes sense.<br />
Just in current enviroment it may be runaway query,<br />
which will take days to execute for some engines&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-721929</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 09 Feb 2010 08:42:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-721929</guid>
		<description>Vadim,

Thanks for you answer. I see your point, though the problem is that queries that do not have any restrictions are essential for answering the following typical business questions (do not know whether they can be answered with the data in your example database):
- How many visits have we had so far in total?
- How many pages has been created?
- What is the distribution of visits per page?
- How has the development of page creations been?

All these sorts of questions run on all the data. I believe that looking at fractions of data is more the IT-perspective on data.</description>
		<content:encoded><![CDATA[<p>Vadim,</p>
<p>Thanks for you answer. I see your point, though the problem is that queries that do not have any restrictions are essential for answering the following typical business questions (do not know whether they can be answered with the data in your example database):<br />
- How many visits have we had so far in total?<br />
- How many pages has been created?<br />
- What is the distribution of visits per page?<br />
- How has the development of page creations been?</p>
<p>All these sorts of questions run on all the data. I believe that looking at fractions of data is more the IT-perspective on data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-721880</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Tue, 09 Feb 2010 03:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-721880</guid>
		<description>David,

I added your query, but I&#039;d like to have at least date restriction,
as we may have different amount of data loaded into fact table, depending on scale factor.</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>I added your query, but I&#8217;d like to have at least date restriction,<br />
as we may have different amount of data loaded into fact table, depending on scale factor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-721733</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 08 Feb 2010 15:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-721733</guid>
		<description>I&#039;d like to see the performance of the following query:
SELECT project_id, sum(page_count) sm
FROM pagestat
GROUP BY project_id;


This query is important to me because it look at ALL the data in the fact table without any joins. This sort of queries gives an overview of all data, which is typical in my field of data mining. I suspect that row-based engines will perform better for this one.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to see the performance of the following query:<br />
SELECT project_id, sum(page_count) sm<br />
FROM pagestat<br />
GROUP BY project_id;</p>
<p>This query is important to me because it look at ALL the data in the fact table without any joins. This sort of queries gives an overview of all data, which is typical in my field of data mining. I suspect that row-based engines will perform better for this one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Wultsch</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-717393</link>
		<dc:creator>Rob Wultsch</dc:creator>
		<pubDate>Mon, 01 Feb 2010 08:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-717393</guid>
		<description>Vadim,
I dropped a note to the PG advocacy list in hopes of getting an expert to help with tuning.

I *wish* I was (and hope to be someday) that expert.</description>
		<content:encoded><![CDATA[<p>Vadim,<br />
I dropped a note to the PG advocacy list in hopes of getting an expert to help with tuning.</p>
<p>I *wish* I was (and hope to be someday) that expert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jos van Dongen</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-717354</link>
		<dc:creator>Jos van Dongen</dc:creator>
		<pubDate>Mon, 01 Feb 2010 07:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-717354</guid>
		<description>Hi Vadim,

Sounds great! What kind of box will you be using and how much memory/nr of disks will it have? E.g. Infobright compresses data quite aggressively so your 172GB will probably fit in 64 or even 32GB of memory, and Greenplum likes lots of disks (at least 1 data segment per CPU core, so with a dual quadcore machine you get better results with 8 partitions on separate drives). What you should also try to do is simulate concurrent access by firing multiple concurrent query streams. Some database are fast when running one query at a time but get crippled when the have to perform multiple tasks simultaneously. 
 
About the &#039;holy wars&#039; you mention: look at http://bit.ly/caLeRF where I ran TPCH using Greenplum and got discussions between PostgreSQL and GP advocates... 

anyway, good luck with the benchmark and if you need help (or access to my machine ;-), just let me know.

best, Jos</description>
		<content:encoded><![CDATA[<p>Hi Vadim,</p>
<p>Sounds great! What kind of box will you be using and how much memory/nr of disks will it have? E.g. Infobright compresses data quite aggressively so your 172GB will probably fit in 64 or even 32GB of memory, and Greenplum likes lots of disks (at least 1 data segment per CPU core, so with a dual quadcore machine you get better results with 8 partitions on separate drives). What you should also try to do is simulate concurrent access by firing multiple concurrent query streams. Some database are fast when running one query at a time but get crippled when the have to perform multiple tasks simultaneously. </p>
<p>About the &#8216;holy wars&#8217; you mention: look at <a href="http://bit.ly/caLeRF" rel="nofollow">http://bit.ly/caLeRF</a> where I ran TPCH using Greenplum and got discussions between PostgreSQL and GP advocates&#8230; </p>
<p>anyway, good luck with the benchmark and if you need help (or access to my machine <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> , just let me know.</p>
<p>best, Jos</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-717246</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Mon, 01 Feb 2010 02:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-717246</guid>
		<description>Rob,

There are two factors:
1) I am not expert in PostgreSQL
2) Results, which directly compare PostregSQL vs MySQL, usually cause holy wars, and one who presents them, is claimed unqualified a) in PostgreSQL, b) in MySQL, c) in both.
So I do not want to go that way.

However if there is expert who wants to install PostgreSQL, tune it, and run proposed scenarios,
I would be happy to even provide access to box.</description>
		<content:encoded><![CDATA[<p>Rob,</p>
<p>There are two factors:<br />
1) I am not expert in PostgreSQL<br />
2) Results, which directly compare PostregSQL vs MySQL, usually cause holy wars, and one who presents them, is claimed unqualified a) in PostgreSQL, b) in MySQL, c) in both.<br />
So I do not want to go that way.</p>
<p>However if there is expert who wants to install PostgreSQL, tune it, and run proposed scenarios,<br />
I would be happy to even provide access to box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Slapo</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-716909</link>
		<dc:creator>Slapo</dc:creator>
		<pubDate>Sun, 31 Jan 2010 14:53:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-716909</guid>
		<description>Vadim,

I suggested what I wrote before because someone actually might want to do some analytics on a cms or an e-shop - visits, visitors, countries, extensive products history, etc.
I see your point of it being perhaps too lengthy to bother with it, though.</description>
		<content:encoded><![CDATA[<p>Vadim,</p>
<p>I suggested what I wrote before because someone actually might want to do some analytics on a cms or an e-shop &#8211; visits, visitors, countries, extensive products history, etc.<br />
I see your point of it being perhaps too lengthy to bother with it, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Wultsch</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-716441</link>
		<dc:creator>Rob Wultsch</dc:creator>
		<pubDate>Sat, 30 Jan 2010 20:27:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-716441</guid>
		<description>Vadim,
I was suggest testing Postgres because I imagine it would have very little increased difficulty over testing Greenplum. I do not think that you are incorrect in that performance would probably be lacking, I just thought that it would be another interesting baseline.</description>
		<content:encoded><![CDATA[<p>Vadim,<br />
I was suggest testing Postgres because I imagine it would have very little increased difficulty over testing Greenplum. I do not think that you are incorrect in that performance would probably be lacking, I just thought that it would be another interesting baseline.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2010/01/28/new-olap-wikistat-benchmark-introduction-and-call-for-feedbacks/comment-page-1/#comment-716036</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Fri, 29 Jan 2010 23:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2160#comment-716036</guid>
		<description>Slapo,

I do not think db design in CMS suitable for OLAP benchmarks.
Either I do not think OLTP oriented FireBird and PostgresSQL will be good for proposed benchmark.

I expect that queries will take 5-1000 mins to execute, and if we do not use special engine,
it will be just pain. I am going to ran on MySQL MyISAM / InnoDB only to have baseline.</description>
		<content:encoded><![CDATA[<p>Slapo,</p>
<p>I do not think db design in CMS suitable for OLAP benchmarks.<br />
Either I do not think OLTP oriented FireBird and PostgresSQL will be good for proposed benchmark.</p>
<p>I expect that queries will take 5-1000 mins to execute, and if we do not use special engine,<br />
it will be just pain. I am going to ran on MySQL MyISAM / InnoDB only to have baseline.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

