| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Zeugswetter Andreas DAZ SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | Ron Peacetree <rjpeace(at)earthlink(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] A Better External Sort? |
| Date: | 2005-10-06 16:54:30 |
| Message-ID: | 434556C6.7010905@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas,
> pg relys on the OS readahead (== larger block IO) to do efficient IO.
> Basically the pg scan performance should match a dd if=file of=/dev/null
> bs=8k,
> unless CPU bound.
FWIW, we could improve performance by creating larger write blocks when
appropriate, particularly on Unixes like Solaris. But that's a bad
effort/result tradeoff for most OSes, so it's not the route I'd be
suggesting for general scans.
However, the external sort code could possibly be improved by more
appropriate block sizing, which I think someone has already suggested.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-10-06 16:57:30 | Re: [PERFORM] A Better External Sort? |
| Previous Message | Martijn van Oosterhout | 2005-10-06 16:06:28 | Re: execution of nested loop joins |