From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org>, Ron Peacetree <rjpeace(at)earthlink(dot)net>, pgsql-hackers(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: [HACKERS] A Better External Sort? |
Date: | 2005-10-03 20:40:29 |
Message-ID: | 200510031340.29376.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Tom,
> Raising work_mem to a gig should result in about five runs, needing only
> one pass, which is really going to be as good as it gets. If you could
> not see any difference then I see little hope for the idea that reducing
> the number of merge passes will help.
Right. It *should have*, but didn't seem to. Example of a simple sort
test of 100 million random-number records
1M 3294 seconds
16M 1107 seconds
256M 1209 seconds
512M 1174 seconds
512M with 'not null' for column that is indexed 1168 seconds
> Umm ... you were raising maintenance_work_mem, I trust, not work_mem?
Yes.
>
> We really need to get some hard data about what's going on here. The
> sort code doesn't report any internal statistics at the moment, but it
> would not be hard to whack together a patch that reports useful info
> in the form of NOTICE messages or some such.
Yeah, I'll do this as soon as the patch is finished. Always useful to
gear up the old TPC-H.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Jeffrey W. Baker | 2005-10-03 20:42:31 | Re: [HACKERS] A Better External Sort? |
Previous Message | Hannu Krosing | 2005-10-03 20:35:33 | Re: effective SELECT from child tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeffrey W. Baker | 2005-10-03 20:42:31 | Re: [HACKERS] A Better External Sort? |
Previous Message | Josh Berkus | 2005-10-03 20:34:01 | Re: [HACKERS] A Better External Sort? |