Re: pgbench - allow to create partitioned tables
От | Fabien COELHO |
---|---|
Тема | Re: pgbench - allow to create partitioned tables |
Дата | |
Msg-id | alpine.DEB.2.21.1907240823060.10384@lancre обсуждение исходный текст |
Ответ на | Re: pgbench - allow to create partitioned tables (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: pgbench - allow to create partitioned tables
Re: pgbench - allow to create partitioned tables |
Список | pgsql-hackers |
Hello Simon, >> While doing some performance tests and reviewing patches, I needed to >> create partitioned tables. Given the current syntax this is time >> consumming. > > Good idea. I wonder why we didn't have it already. Probably because I did not have to create partitioned table for some testing:-) >> sh> pgench -i -s 1 --partition-number=$N --partition-type=hash > > Given current naming of options, I would call this > --partitions=number-of-partitions and --partition-method=hash Ok. >> # then run >> sh> pgench -S -M prepared -P 1 -T 10 >> >> # and look at latency: >> # no parts = 0.071 ms >> # 1 hash = 0.071 ms (did someone optimize this case?!) >> # 2 hash ~ 0.126 ms (+ 0.055 ms) >> # 50 hash ~ 0.155 ms >> # 100 hash ~ 0.178 ms >> # 150 hash ~ 0.232 ms >> # 200 hash ~ 0.279 ms >> # overhead ~ (0.050 + [0.0005-0.0008] * nparts) ms > > It is linear? Good question. I would have hoped affine, but this is not very clear on these data, which are the median of about five runs, hence the bracket on the slope factor. At least it is increasing with the number of partitions. Maybe it would be clearer on the minimum of five runs. -- Fabien.
Вложения
В списке pgsql-hackers по дате отправления: