From: <gnuoytr@rcn.com>
Subject: Re: MemSQL the "world's fastest
 database"?
To: pgsql-performance@postgresql.org
MIME-Version: 1.0
In-Reply-To: <4FE899CE.60901@optionshouse.com>
References: 
 <CAFwQ8rcpbZsR3Ndk8GoVsqGhc8y+M8siBmMDN1X=mom4uAO8ZQ@mail.gmail.com>
	<4FE899CE.60901@optionshouse.com>
Message-Id: <201206251802.060128@ms20.lnh.mail.rcn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 25 Jun 2012 14:02:41 -0400 (EDT)


---- Original message ----
>Date: Mon, 25 Jun 2012 12:03:10 -0500
>From: pgsql-performance-owner@postgresql.org (on behalf of Shaun Thomas <sthomas@optionshouse.com>)
>Subject: Re: [PERFORM] MemSQL the "world's fastest database"?  
>To: Craig James <cjames@emolecules.com>
>Cc: <pgsql-performance@postgresql.org>
>
>On 06/25/2012 11:25 AM, Craig James wrote:
>
>> Any thoughts about this? It seems to be a new database system designed
>> from scratch to take advantage of the growth in RAM size (data sets that
>> fit in memory) and the availability of SSD drives. It claims to be "the
>> world's fastest database."
>
>I personally don't put a lot of stock into this. You can get 90k+ TPS 
>from an old PostgreSQL 8.2 install if it's all in memory. High 
>transactional output itself isn't substantially difficult to achieve.
>
>I'm also not entirely certain how this is different from something like 
>VoltDB, which also acts as an in-memory database with high TPS throughput.
>
>Then there's this from the article:
>
>"The key ideas are that SQL code is translated into C++, so avoiding the 
>need to use a slow SQL interpreter, and that the data is kept in memory, 
>with disk read/writes taking place in the background."
>
>Besides the nonsense statement that SQL is translated to C++ (Lexical 
>scanners would circumvent even this step, and does that mean you have to 
>literally compile the resulting C++? Ridiculous.) This violates at least 
>the 'D' tenet of ACID. Fine for transient Facebook data, but not going 
>anywhere near our systems.

DB2 on the mainframe (if memory serves), for one, will compile static SQL to machine code.  Not that unusual.

http://www.mainframegurukul.com/tutorials/database/db2_tutorials/DB2Precompilebind.html

http://www.mainframegurukul.com/tutorials/database/db2_tutorials/sample-db2-cobol-compile-jcl.html


>
>-- 
>Shaun Thomas
>OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
>312-444-8534
>sthomas@optionshouse.com
>
>______________________________________________
>
>See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
>
>-- 
>Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-performance