pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: Richard Huxton <dev@archonet.com>
Cc: Postgres Performance <pgsql-performance@postgresql.org>
Subject: Re: select count(*)  very slow on an already vacuumed table.
Date: Thu, 15 Apr 2004 16:01:26 +0530
Message-ID: <407E647E.7090207@trade-india.com> (raw)
In-Reply-To: <200404150853.32475.dev@archonet.com>
References: <407D7A89.60508@trade-india.com>
	<200404142008.58533.dev@archonet.com>
	<407E3563.6000408@trade-india.com>
	<200404150853.32475.dev@archonet.com>

Richard Huxton wrote:

>On Thursday 15 April 2004 08:10, Rajesh Kumar Mallah wrote:
>  
>
>>The problem is that i want to know if i need a Hardware upgrade
>>at the moment.
>>
>>Eg i have another table rfis which contains ~ .6 million records.
>>    
>>
>
>  
>
>>SELECT count(*) from rfis where sender_uid > 0;
>>    
>>
>
>  
>
>>Time: 117560.635 ms
>>
>>Which is approximate 4804 records per second. Is it an acceptable
>>performance  on the hardware below:
>>
>>RAM: 2 GB
>>DISKS: ultra160 , 10 K  , 18 GB
>>Processor: 2* 2.0 Ghz Xeon
>>    
>>
>
>Hmm - doesn't seem good, does it? If you run it again, is it much faster 
>(since the data should be cached then)? What does "vmstat 10" show while 
>you're running the query?
>
>One thing you should have done is read the performance tuning guide at:
>  http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php
>The default values are very conservative, and you will need to change them.
>  
>
Hi,

Thanks for the interest . my config are not the default ones.
i was running iostat while running the query. Looks like one
of the disks doesnt' go past a read performance of 20 ,000 KBytes/sec

while the other disk  it goes as high as 40,000 . What i am ding 
currently is
loading the table in both the disks and compare the table scan speeds.

The performance is definitely better in the newly loaded table in the other
disk . the load in server is 13 because i am simultaneously re-loading 
the data
in other table.


rt2=# SELECT count(*) from rfis where sender_uid > 0;
+--------+
| count  |
+--------+
| 564870 |
+--------+
(1 row)

Time: 10288.359 ms

rt2=#

shall post the comparitive details under normal load soon


regds
mallah.







>  
>
>>What kind of upgrades shoud be put on the server for it to become
>>reasonable fast.
>>    
>>
>
>If you've only got one disk, then a second disk for OS/logging. Difficult to 
>say more without knowing numbers of users/activity etc.
>
>  
>




view thread (7+ messages)

Message-ID: <407E647E.7090207@trade-india.com>
Permalink:  ../407E647E.7090207@trade-india.com/
Also on:    postgresql.org/message-id/407E647E.7090207@trade-india.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mallah@trade-india.com, dev@archonet.com
  Subject: Re: select count(*)  very slow on an already vacuumed table.
  In-Reply-To: <407E647E.7090207@trade-india.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox