Re: Performance die when COPYing to table with bigint PK

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



04.08.11 18:59, Kevin Grittner написав(ла):
Robert Ayrapetyan<robert.ayrapetyan@xxxxxxxxxx>  wrote:
Kevin Grittner<Kevin.Grittner@xxxxxxxxxxxx>  wrote:

[regarding tests which do show the problem]
tried same with 2 columns (bigint and int) - it didn't produced
such effect probably because data volume has critical effect.

Based on what you're showing, this is almost certainly just a matter
of pushing your volume of active data above the threshold of what
your cache holds, forcing it to do disk access rather than RAM
access for a significant portion of the reads.

-Kevin
Yep. Seems so. Plus famous "you'd better insert data, then create indexes".
On my database it takes twice the time for int8 then for int4 to insert data. Also it takes ~twice a time (2 hours) to add 200K of rows to 200M of rows than to make an index over 200M of rows (1 hour).

Best regards, Vitalii Tymchyshyn

--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux