Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 6DD33603DC3 for ; Sun, 1 Jul 2012 01:19:00 -0300 (ADT) Received: from moutng.kundenserver.de ([212.227.126.187]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SlBcg-0001gk-3Y for pgsql-performance@postgresql.org; Sun, 01 Jul 2012 04:18:59 +0000 Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MPZwH-1SpKM92ntB-004hKD; Sun, 01 Jul 2012 06:18:44 +0200 Message-ID: <4FEFCFA3.50305@2ndQuadrant.com> Date: Sun, 01 Jul 2012 00:18:43 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: MemSQL the "world's fastest database"? References: <4FE8582F0200002500048AAD@gw.wicourts.gov> In-Reply-To: <4FE8582F0200002500048AAD@gw.wicourts.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:d8L0UmxFBPypPYITlamhYu8BVDhgmQt5nuw8wjW/JhG R5eYa0c7NlelnvVDuP/3QZXeNfd70pMPuPM9BTDNOzl1SdWJYf IDQbq1YF1dyGd182RwPU/r8pVToyZy9D1+ueyxXufNGIGt9swD I0MuaSaWlep8Dy7GwMJoOGQFHTatlYCtG5wwUXDq5vVtKOsHjT q46gS2Tx6QF/KEomYxyl3D9kr9QIRP6RCkdVn7WLZLDTOUP6vE iY3DC69KkwvAChRaZXye49EFfcMUzAYe5YVLkz27Oc+7eFASL/ px+DJ1xb28NHn7sJ29lV1Zq0MkxsBfHYOT36x59Y//vPxee18r XLAqTAaPi1n3Z1KTcJ1k= X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/1 X-Sequence-Number: 47182 On 06/25/2012 01:23 PM, Kevin Grittner wrote: > Craig James wrote: > >> It claims to be "the world's fastest database." > >> [link where they boast of 80,000 tps read-only] > > 20,000 tps? Didn't we hit well over 300,000 tps in read-only > benchmarks of PostgreSQL with some of the 9.2 performance > enhancements? It's 20K TPS on something that MySQL will only do 3.5 TPS. The queries must be much heavier than the ones PostgreSQL can get 200K+ on. We'd have to do a deeper analysis of the actual queries used to know exactly how much heavier though. They might be the type MySQL is usually faster than PostgreSQL on (i.e. ones using simple operations and operators), or they could be ones where PostgreSQL is usually faster than MySQL (i.e. more complicated joins). All I can tell you for sure if that they used a query mix that makes MemSQL look much faster than MySQL. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com