| From: | Luis Amigo <lamigo(at)atc(dot)unican(dot)es> |
|---|---|
| To: | jussi(dot)mikkola(at)bonware(dot)com |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org, inxc(at)itmeedia(dot)ee |
| Subject: | Re: 7.2 is slow? |
| Date: | 2001-12-19 15:20:40 |
| Message-ID: | 3C20B048.BC58DC4D@atc.unican.es |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
We're getting similar problem.
We're currently working on TPC-H benchmarking using postgresql 7.2b3.
>From one up to 8 paralell conexions (we've got 8 MIPS processors), uptime
increases from 1 to 8,
but increasing above 8 makes performance drop rapidly to uptimes even lower
than 2 for 22 conexions.
As we've could trail, when we have more processes than processors, we're
getting an increasing number of collisions.
when collision happens both processes get idle for a while, then collision may
happen again and so...
Regards
Luis Amigo
Universidad de Cantabria
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-12-19 15:30:51 | Re: 7.2 is slow? |
| Previous Message | Ashley Cambrell | 2001-12-19 15:09:42 | Re: 7.2 is slow? |