Re: Insertions slower than Updates?

Ofer Israeli  wrote:
 
> INSERT should be cheaper than UPDATE due to only dealing with one 
> record instead of two.
 
... unless the UPDATE is a HOT update, in which case the indexes
don't need to be touched.
 
> Anyone have any ideas on why the empty db is giving worse
> results??
 
Besides the HOT updates being fast, there is the issue of having
space already allocated and ready for the database to use, rather
than needing to make calls to the OS to create and extend files as
space is needed.
 
-Kevin