Thread: is insertion and movement times are correlated to the size of the database?
is insertion and movement times are correlated to the size of the database?
From
"Kalle Barck-Holst"
Date:
Hi I am doing a research project on real time robotics and wanted to have the postgres as a database to save measurements weaggregate when running our robots. A common operation we do is insertion and movements of measurements within tables. But it seams as if insertion and movementtimes are correlated to the size of the database. Can this be possible? IE inserting into a large database takeslonger time than into a small database. I'd be grateful for comments on the reason for this. Carl Barck-Holst Carl och Josefine Barck-Holst Östermalms g 84 11450 Stockholm 08 6679904 Carl 070-2642506 Josefine 073-9648103
On Mon, 2002-12-09 at 01:30, Kalle Barck-Holst wrote: > Hi > > I am doing a research project on real time robotics and wanted to have the postgres as a database to save measurementswe aggregate when running our robots. > > A common operation we do is insertion and movements of measurements within tables. But it seams as if insertion and movementtimes are correlated to the size of the database. Can this be possible? IE inserting into a large database takeslonger time than into a small database. If there are any indexes or constraints, then definitely. The insert really doesn't have additional overhead for the size of the DB, but the work involved for most constraints and indexes do. -- Rod Taylor <rbt@rbt.ca> PGP Key: http://www.rbt.ca/rbtpub.asc