Re: [PERFORM] UPDATE 66k rows too slow

2008-03-10 Thread Greg Smith
On Mon, 10 Mar 2008, Miguel Arroz wrote: I deleted the DB, created a new one and generated new test data. I know have 72k rows, and the same query finishes in... 9 seconds. This seems like more evidence that your problem here is related to dead rows (this is what Andrew suggested). If a fres

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-10 Thread Miguel Arroz
Hi! The disk subsystem will be a RAID 1, but for now it's just a single 7200 rpm 160 GB SATA hard drive. The PgSQL version is 8.3, the latest one. I have done some performance tests on the drive, and it handles about 40 MB/s on sequential writes, so I'm assuming it's OK. Yours Mi

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-10 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Mar 2008 23:46:10 + Miguel Arroz <[EMAIL PROTECTED]> wrote: tty ad4 ad6 cpu > tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id > 0 60 33.48 449 14.66 0.00 0 0.00 11 0

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-10 Thread Miguel Arroz
Hi! It now raised to 40 seconds... here goes the result of iostat: iostat -K -c 40 tty ad4 ad6 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 1 78 32.86 34 1.08 0.70 0 0.00 13 0 1 0 86 0 180 6.00 4 0.02 0.00

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-10 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Mar 2008 23:17:54 + Miguel Arroz <[EMAIL PROTECTED]> wrote: > Hi! > >I read and did many stuff you pointed me too. Raised shared > buffers to 180 MB, and tried again. Same results. > >I deleted the DB, created a new one and ge

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-10 Thread Miguel Arroz
Hi! I read and did many stuff you pointed me too. Raised shared buffers to 180 MB, and tried again. Same results. I deleted the DB, created a new one and generated new test data. I know have 72k rows, and the same query finishes in... 9 seconds. I'm totally clueless. Anyway, two que

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-09 Thread Greg Smith
On Mon, 10 Mar 2008, Miguel Arroz wrote: My question is, how can I "ask" PgSQL what's happening? How can I avoid guessing, and be sure of what is causing this slowdown? There are many pieces involved here, and any one or multiple of them could be to blame. Someone may make a guess and get lu

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-09 Thread Tom Lane
Miguel Arroz <[EMAIL PROTECTED]> writes: > EXPLAIN ANALYZE UPDATE text_answer_mapping_ebt SET f1 = false; > QUERY PLAN > -

Re: [PERFORM] UPDATE 66k rows too slow

2008-03-09 Thread andrew
Miguel Arroz <[EMAIL PROTECTED]> wrote .. >I'm testing an update on 66k rows on Postgresql, and it seems > something is not right here. > >My server is a Quad-Xeon 3.2 Ghz with 2 GB RAM and a RAID 1 running > FreeBSD 6.3 and PgSQL 8.3. My development machine is a PowerBook G4 > 1.67 G