Re: new vacuum is slower for small tables
От | Tom Lane |
---|---|
Тема | Re: new vacuum is slower for small tables |
Дата | |
Msg-id | 513.1228767634@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: new vacuum is slower for small tables ("Pavel Stehule" <pavel.stehule@gmail.com>) |
Ответы |
Re: new vacuum is slower for small tables
|
Список | pgsql-hackers |
"Pavel Stehule" <pavel.stehule@gmail.com> writes: > It's strange, when I repeat tests, I get usually times about 10 ms, > but cca cca every 5 test it is about 2ms Hmm. The theory I'd developed for what I see here is that the "slow" timings correspond to when the pgstat code decides it needs a new stats file (and so it has to signal the stats collector and wait for the file to show up). The "fast" timings occur if the existing stats file is considered fresh enough to re-use. Hence, it's "fast" if you re-execute the VACUUM within half a second of the previous one, else slow. I can't tell if that's the same thing you see or not. Now that we have the flexibility to allow different levels of stats stale-ness for different callers, I wonder whether it wouldn't be okay to let pgstat_vacuum_stat work with quite stale files, eg up to a minute or so. regards, tom lane
В списке pgsql-hackers по дате отправления: