Re: [GENERAL] vacuum of empty table slows down as database tablecount grows
От | marcin kowalski |
---|---|
Тема | Re: [GENERAL] vacuum of empty table slows down as database tablecount grows |
Дата | |
Msg-id | CABKsJ=THTur8MRXWtigjptSzKRyZZ1CWD_uHYT_U=5JzcForFA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] vacuum of empty table slows down as database tablecount grows (marcin kowalski <yoshi314@gmail.com>) |
Список | pgsql-general |
Well, unfortunately i am not seeing much difference. I shaved off maybe a second of worst case run.
I guess i should just split the db into smaller ones, since tmpstats are now per-db. Are there any other things i could try?
I guess i should just split the db into smaller ones, since tmpstats are now per-db. Are there any other things i could try?
2017-01-05 8:18 GMT+01:00 marcin kowalski <yoshi314@gmail.com>:
Thanks, i'll redo the benchmarks and report back how things look now.2017-01-04 20:33 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
>
> This is irrelevant of amount of data restored, i am seeing the same behavior with just schema restore, as well as with schema+data restores.
>
> If anyone is interested i may upload the schema data + my benchmarking script with collected whisper data from my test run (i've been plotting it in grafana via carbon)
>
> Is this a known issue? Can i do anything to improve performance here?we had 10K and more tables in one database - and we had lot of issues.I know so Tomas fixed some issues, but we need the stat files in tmpfsplease, read this article https://blog.pgaddict.com/posts/the-two-kinds-of-stats-in-p ostgresql RegardsPavel>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: