| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "P(dot)J(dot) \"Josh\" Rovero" <rovero(at)sonalysts(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Solaris Performance |
| Date: | 2002-02-04 21:12:13 |
| Message-ID: | 12313.1012857133@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"P.J. \"Josh\" Rovero" <rovero(at)sonalysts(dot)com> writes:
> For non-postgresql applications, the Suns are
> typically faster than the HPs. While direct
> comparisons are always dangerous, the SPARC
> chips are clocked at about 2-3 times what
> the PA-RISC chips are.
> The postgresql performance on Solaris is
> an order of magnitude (10x) slower than
> Linux x86 at same CPU clock speed.
Hmm. So can you figure out where the time is going? What do you see
with top, iostat, vmstat, ...? Can you recompile with profiling (gmake
clean, gmake PROFILE=-pg all typically works on gcc platforms) and learn
something about where the backend is spending its time?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-04 21:27:48 | Re: Solaris Performance |
| Previous Message | P.J. "Josh" Rovero | 2002-02-04 21:07:31 | Re: Solaris Performance |