Received: from sivka.carrier.kiev.ua (root@sivka.carrier.kiev.ua [193.193.193.101]) by hub.org (8.10.1/8.11.0) with ESMTP id e9SL1NZ70169 for ; Sat, 28 Oct 2000 17:01:25 -0400 (EDT) (envelope-from evpopkov@carrier.kiev.ua) Received: from planka.carrier.kiev.ua (root@users.lucky.net [193.193.193.106]) by sivka.carrier.kiev.ua (8/Kilkenny_is_better) with ESMTP id AAN83570 for ; Sun, 29 Oct 2000 00:01:19 +0300 (EEST) (envelope-from evpopkov@carrier.kiev.ua) Received: from ed.ed (ln2-66.users.lucky.net [193.193.199.66]) by planka.carrier.kiev.ua (8) with ESMTP id AAM26513 for ; Sun, 29 Oct 2000 00:01:17 +0300 (EEST) (envelope-from evpopkov@carrier.kiev.ua) Received: (from root@localhost) by ed.ed (8.8.7/8.8.5) id VAA00827 for pgsql-sql@postgresql.org; Sat, 28 Oct 2000 21:00:05 GMT From: KuroiNeko Date: Sat, 28 Oct 2000 21:00:05 +0000 To: pgsql-sql@postgresql.org Subject: Re: benchmarks Message-ID: <39FB3E55.nailLJ1IK8VB@ed.ed> References: <200010271836.e9RIaNZ96055@hub.org> <39FA7133.AEEE0D40@agliodbs.com> User-Agent: nail 9.14 2000-06-26 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200010/266 X-Sequence-Number: 1933 > Comparing PostgreSQL to MySQL is like comparing an 18-wheel Kenworth to > a Porsche. The two are not equivalent That's it. Major differences in features makes any benchmarking `apples to oranges.' > ... if you want a simple, very > very fast READ-ONLY database, use MySQL. BTW, can it be used on a r/o partition, or it still writes something to the files (locks, stats)? > If you want a full-featured transaction-environment database for a huge, > complex set of data, use PostgreSQL. Even if the system is relatively small and simple.... Everything will go down in fires, this is the law. So, the first thing to think about is what will your options be when you're trying to keep the parts. Stress and torture tests would be more usefull than benchmarking. > Any benchmarks you find are likely comapring the two for hosting web > sites, which is unfair to PostgreSQL. IIRC, there was one in favor PGSQL (wasn't it run by the Bridge?). However, the very fact of benchmarking these two along with non-disclosed commercial products, where PGSQL wins with flying colours, IMHO does more harm than good. > If everything your database needs > to do is serve up page content, go for MySQL. How 'bout flat files? They will be even faster. Main advantage of DBMS, as I see it, is a possibility to build searchable, logically connected structures, with consistency and concurrency supported on the server side. With MySQL one has neither referential integrity, nor server side logic. Moreof, HTML pages are bad as textual attributes even when tuple/page size limitation can be easily worked around. If you want dynamic content, SSI and CGI will do, and there's nothing about DBMS. Storing page templates as BLOBs gives nothing but slowdown. > If you've got to build a 60-user inventory management system, > MySQL won't even bring you close - heck, it's not even close to > SQL92-compliant. It's still possible, one can even get it for $ 200, but TCO will sky rocket when it starts to phreak, or when business rules will be changed. -- contaminated fish and microchips huge supertankers on Arabian trips oily propaganda from the leaders' lips all about the future there's people over here, people over there everybody's looking for a little more air crossing all the borders just to take their share planning for the future Rainbow, Difficult to Cure