X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 66C7BD1B1DC for ; Wed, 2 Jun 2004 11:28:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 58132-02 for ; Wed, 2 Jun 2004 14:28:32 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id A320AD1B173 for ; Wed, 2 Jun 2004 11:28:27 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1BVWiP-0008Dt-00; Wed, 02 Jun 2004 10:27:37 -0400 To: Vitaly Belman Cc: pgsql-performance@postgresql.org, Bryan Encina , Matthew Nuzum Subject: Re: PostgreSQL on VMWare vs Windows vs CoLinux References: <16113857921.20040602015607@012.net.il> In-Reply-To: <16113857921.20040602015607@012.net.il> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 02 Jun 2004 10:27:36 -0400 Message-ID: <87n03m592f.fsf@stark.xeocode.com> Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200406/7 X-Sequence-Number: 7065 Vitaly Belman writes: > With all that said, VMWare is badly suited for running a database, > while CoLinux can be run as a service (didn't try it yet though), > VMWare always sits there, it is slow to go up, slow to go down and > generally feels like a system hog. Uhm, it sounds like you're using VMWare Workstation? VMWare has a range of different versions including some that are specifically targeted towards server situations. I think they had the idea that hosting companies would run hundreds of virtual machines on a server and provide their hosting clients with a virtual machine to play with. That said, I'm curious why the emulated servers performed better than the Native Windows port. My first thought is that they probably aren't syncing every write to disk so effectively they're defeating the fsyncs, allowing the host OS to buffer disk writes. I would be curious to see better stats on things like a pgbench run which would give some idea of the context switch efficiency, and a large select or update, which would give some idea of the i/o throughput. Really there's no excuse for the Windows port to be slower than an emulator. Barring effects like the disk caching I mentioned, it should far outpace the emulators. -- greg