I repeat your test on ProLiant DL580 Gen9 with Xeon E7-8890 v3.
pgbench -s 100 and command vacuum pgbench_acounts after 10_000 transactions:
with: alter system set vacuum_cost_delay to DEFAULT;
parallel_vacuum_workers | time
1 | 138.703,263 ms
2 | 83.
This is obviously a bug because without "concurrently" create index this do
not reproduce.
---
Dmitry Vasilyev
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
2016-02-26 16:36 GMT+03:00 Alexander Korotkov :
> On Fri, Feb 26, 2016 at 3:41 PM, Вас
Session opened on replica doesn't see concurrently created indexes at this
time on master.
We have master and replica:
1. master: pgbench -i -s 10
2. replica:
explain (analyze,verbose) select * from pgbench_accounts where abalance = 1;
3. master:
ALTER INDEX pgbench_accounts_abalance_idx RENAME
2015-12-25 22:42 GMT+03:00 Васильев Дмитрий :
>
>
>
> 2015-12-25 21:28 GMT+03:00 Tom Lane :
>
>> Andres Freund writes:
>> > On December 25, 2015 7:10:23 PM GMT+01:00, Tom Lane
>> wrote:
>> >> Seems like what you've got here is a ker
2015-12-25 21:28 GMT+03:00 Tom Lane :
> Andres Freund writes:
> > On December 25, 2015 7:10:23 PM GMT+01:00, Tom Lane
> wrote:
> >> Seems like what you've got here is a kernel bug.
>
> > I wouldn't go as far as calling it a kernel bug. Were still doing 300k
> tps. And were triggering the perfo
2015-12-25 20:44 GMT+03:00 Andres Freund :
> On December 25, 2015 6:27:06 PM GMT+01:00, "Васильев Дмитрий"
> >>If so, could you provide a hierarchical before/after profile?
> >
> >Performance | Git hash commit| Date
> >~ 360k tps | c3e7c24a1d60d
2015-12-25 20:27 GMT+03:00 Васильев Дмитрий :
>
> 2015-12-25 20:18 GMT+03:00 Andres Freund :
>
>> On December 25, 2015 6:08:15 PM GMT+01:00, "Васильев Дмитрий" <
>> d.vasil...@postgrespro.ru> wrote:
>> >Hello hackers!
>> >
>> >
2015-12-25 20:18 GMT+03:00 Andres Freund :
> On December 25, 2015 6:08:15 PM GMT+01:00, "Васильев Дмитрий" <
> d.vasil...@postgrespro.ru> wrote:
> >Hello hackers!
> >
> >I suddenly found commit ac1d794 gives up to 3 times performance
> >degradation.
Hello hackers!
I suddenly found commit ac1d794 gives up to 3 times performance degradation.
I tried to run pgbench -s 1000 -j 48 -c 48 -S -M prepared on 70 CPU-core
machine:
commit ac1d794 gives me 363,474 tps
and previous commit a05dc4d gives me 956,146
and master( 3d0c50f ) with revert ac1d794