From: | Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | AW: AW: [HACKERS] sort on huge table |
Date: | 1999-11-02 16:08:14 |
Message-ID: | 219F68D65015D011A8E000006F8590C60339E160@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> > This new test case is not big enough to show cache memory
> contention,
> > and is thus faster with the new code.
>
> Cache memory contention? I don't think so. Take a look at the CPU
> versus elapsed times in Tatsuo's prior report on the 2Gb case.
> I'm not sure yet what's going on, but it's clear that the
> bottleneck is
> I/O operations not processor/memory speed.
Yes, I doubt that the new test shows the same bottleneck situation.
He did not tell us the IO versus CPU time on the recent 250 Mb test.
I suspect, that the CPU time now has a higher percentage on total time.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | postgres | 1999-11-02 16:34:34 | Re: [GENERAL] users in Postgresql |
Previous Message | Lamar Owen | 1999-11-02 16:04:38 | Re: [HACKERS] Regression Testing on REL6_5_PATCHES |