"Todd A. Cook" writes:
> Todd A. Cook wrote:
>> Tom Lane wrote:
>>> If you have time to repeat the experiments, it would be interesting to
>>> see what happens with consistent default_statistics_target across 8.3
>>> and 8.4.
>>
>> That would seem to be it:
>> 8.4b2 183 min 84,028,8
Todd A. Cook wrote:
Tom Lane wrote:
"Todd A. Cook" writes:
First, the numbers:
PG VersionLoad time pg_database_size autovac
--
8.2.13179 min 92,807,992,820on
8.3.7 180 min 84,048,744
Tom Lane wrote:
"Todd A. Cook" writes:
First, the numbers:
PG VersionLoad time pg_database_size autovac
--
8.2.13179 min 92,807,992,820on
8.3.7 180 min 84,048,744,044on (de
Stefan Kaltenbrunner writes:
> Tom Lane wrote:
>> If you have time to repeat the experiments, it would be interesting to
>> see what happens with consistent default_statistics_target across 8.3
>> and 8.4.
> given that this was likely a single-thread restore and therefor wal
> logged I wonder if
Tom Lane wrote:
"Todd A. Cook" writes:
First, the numbers:
PG VersionLoad time pg_database_size autovac
--
8.2.13179 min 92,807,992,820on
8.3.7 180 min 84,048,744,044on (de
"Todd A. Cook" writes:
> First, the numbers:
> PG VersionLoad time pg_database_size autovac
> --
>8.2.13179 min 92,807,992,820on
>8.3.7 180 min 84,048,744,044on (defaults)
>
Vick Khera wrote:
On Wed, Jun 17, 2009 at 10:50 AM, Todd A.
Cook wrote:
The loads were all done on the same machine, with the DB going on a pair
of SATA drives in a RAID-0 stripe. The machine has 2 non-HT Xeons and
8GB RAM. maintenance_work_mem was set to 512MB in all three cases.
What if yo
There was an interesting presentation at PG Con from a guy at Sun who
did a series of load tests on 8.3 vs 8.4
http://www.pgcon.org/2009/schedule/events/124.en.html
There is a link to the video from that page so you can watch it. But
he found a strange "corner case" where 8.4 performed way worse
On Wed, Jun 17, 2009 at 10:50 AM, Todd A.
Cook wrote:
> The loads were all done on the same machine, with the DB going on a pair
> of SATA drives in a RAID-0 stripe. The machine has 2 non-HT Xeons and
> 8GB RAM. maintenance_work_mem was set to 512MB in all three cases.
What if you double or trip
Hi,
First, the numbers:
PG VersionLoad time pg_database_size autovac
--
8.2.13179 min 92,807,992,820on
8.3.7 180 min 84,048,744,044on (defaults)
8.4b2 206 min 84,0
10 matches
Mail list logo