Re: Sort performance
От | Luke Lonergan |
---|---|
Тема | Re: Sort performance |
Дата | |
Msg-id | 3E37B936B592014B978C4415F90D662D03EA214A@MI8NYCMAIL06.Mi8.com обсуждение исходный текст |
Ответ на | Sort performance (Gregory Stark <stark@enterprisedb.com>) |
Ответы |
Re: Sort performance
|
Список | pgsql-hackers |
What version of pgsql? Recent changes stripped the sort set down considerably in size in external sort, I'm not sure the same is done if the datadoesn't spill to disk. - Luke Sent by GoodLink (www.good.com) -----Original Message----- From: Gregory Stark [mailto:stark@enterprisedb.com] Sent: Friday, September 01, 2006 11:03 AM Eastern Standard Time To: pgsql-hackers Subject: [HACKERS] Sort performance I'm not sure if this is good news or bad news. Either some kudos are due to the gang that worked on the external sort performance or something's very wrong with the qsort implementation in glibc because I'm seeing Postgres's external sort perform better than qsort. This is despite Postgres external sorts having to execute filesystem calls pushing buffers back and forth between user-space and kernel-space, which seems hard to believe. I feel like something's got to be pretty far wrong with the qsort call here for this to be possible. At first I chalked this up to qsort having O(n^2) behaviour occasionally but a) This is glibc where qsort is actually mergesort which should behave pretty similarly to Postgres's mergesort and b) the input data is randomized pretty well so it really ought be a problem even were it qsort. Mem Runs Time ---- ---- ---- 1MB 18 8.25s 10MB 3 5.6s 100MB qsort 6.1s The input is a table with one column, a text field. It contains /usr/share/dict/words ordered by random() and then repeated a bunch of times. (Sorry about the imprecision, I set this table up a while ago and don't remember exactly what I did). a The machine has plenty of RAM and isn't swapping or running any other services. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
В списке pgsql-hackers по дате отправления: