Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns |
Дата | |
Msg-id | 20170915182311.n7ukfdudutqsjyxy@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns (Thom Brown <thom@linux.com>) |
Ответы |
Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns
|
Список | pgsql-hackers |
Hi Thom, Thanks for taking a whack at this! On 2017-09-15 12:16:22 +0100, Thom Brown wrote: > I've run a fairly basic test with a table with 101 columns, selecting > a single row from the table and I get the following results: > > > Columns with 1-character names: > > master (80 jobs, 80 connections, 60 seconds): FWIW, I don't think it's useful to test this with a lot of concurrency - at that point you're likely saturating the machine with context switches etc. unless you have a lot of cores. As this is isn't related to concurrency I'd rather just check a single connection. > transaction type: /tmp/test.sql > scaling factor: 1 > query mode: simple I think you'd need to use prepared statements / -M prepared to see benefits - when parsing statements for every execution the bottleneck is elsewhere (hello O(#available_columns * #selected_columns) in colNameToVar()). Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: