Re: Relation extension scalability
От | Dilip Kumar |
---|---|
Тема | Re: Relation extension scalability |
Дата | |
Msg-id | CAFiTN-tkYR3S_DdF2U9gQbNi7zUEJdQtgcOVHadBcTeVS+d9_w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Relation extension scalability (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: Relation extension scalability
Re: Relation extension scalability |
Список | pgsql-hackers |
On Mon, Mar 28, 2016 at 3:02 PM, Dilip Kumar <dilipbalaut@gmail.com> wrote:
1. Relation Size : No change in size, its same as base and v132. INSERT 1028 Byte 1000 tuple performance-----------------------------------------------------------Client base v13 v151 117 124 1222 111 126 1234 51 128 1258 43 149 13516 40 217 14732 35 263 1413. COPY 10000 Tuple performance.----------------------------------------------Client base v13 v151 118 147 1552 217 276 2734 210 421 4578 166 630 64316 145 813 59532 124 985 598Conclusion:---------------1. I think v15 is solving the problem exist with v13 and performance is significantly high compared to base, and relation size is also stable, So IMHO V15 is winner over other solution, what other thinks ?2. And no point in thinking that V13 is better than V15 because, V13 has bug of sometime extending more than expected pages and that is uncontrolled and same can be the reason also of v13 performing better.
Found one problem with V15, so sending the new version.
In V15 I am taking prev_blkno as targetBlock instead it should be the last block of the relation at that time. Attaching new patch.
--
Вложения
В списке pgsql-hackers по дате отправления: