Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2440C650319 for ; Wed, 23 Jul 2008 13:22:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 62145-05 for ; Wed, 23 Jul 2008 13:22:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id 0751265069B for ; Wed, 23 Jul 2008 12:45:07 -0300 (ADT) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KLgWU-0005hr-QM for pgsql-performance@postgresql.org; Wed, 23 Jul 2008 15:45:02 +0000 Received: from apn-77-112-123-233.gprs.plus.pl ([77.112.123.233]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jul 2008 15:45:02 +0000 Received: from public by apn-77-112-123-233.gprs.plus.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jul 2008 15:45:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-performance@postgresql.org From: Miernik Subject: how to fix problem then when two queries run at the same time, it takes longer to complete then if run in sequence Date: Wed, 23 Jul 2008 17:21:12 +0200 Lines: 22 Message-ID: <20080723152112.30A4.0.NOFFLE@turbacz.local> Reply-To: Miernik X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: apn-77-112-123-233.gprs.plus.pl X-Archive: encrypt=none User-Agent: tin/1.9.3-20080506 ("Dalintober") (UNIX) (Linux/2.6.25-2-686 (i686)) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/215 X-Sequence-Number: 30815 I have a PostgreSQL database on a very low-resource Xen virtual machine, 48 MB RAM. When two queries run at the same time, it takes longer to complete then if run in sequence. Is there perhaps a way to install something like a query sequencer, which would process queries in a FIFO manner, one at a time, even if a new query comes before the last one running is finished, it would not give the new query to the server before the one running now finishes? That would greatly improve performance. Any tips in general for running PostgreSQL on such low-resource machine? I have: shared_buffers = 5MB work_mem = 1024kB are these good values, or could perhaps changing something improve it a bit? Any other parameters to look at? -- Miernik http://miernik.name/