Received: from www-uk-05.digiserve.com ([195.172.23.63]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1OE4ex70197 for ; Sat, 24 Feb 2001 09:04:40 -0500 (EST) (envelope-from dev@archonet.com) Received: from mainbox.archonet.com (mwynhau.demon.co.uk [193.237.186.96]) by www-uk-05.digiserve.com (8.9.1/8.9.1) with ESMTP id OAA16380; Sat, 24 Feb 2001 14:05:27 GMT Received: from archonet.com (ibook.archonet.com [192.168.1.32]) by mainbox.archonet.com (Postfix) with ESMTP id A24AB2A3F8; Sat, 24 Feb 2001 11:23:37 +0000 (GMT) Message-ID: <3A9799B9.43F61817@archonet.com> Date: Sat, 24 Feb 2001 11:23:37 +0000 From: Richard Huxton X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Kevin Quinlan Cc: pgsql-sql@postgresql.org Subject: Re: Estimation of SQL statements References: <000801c099ef$6ace91d0$79ac3318@kquinlan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200102/382 X-Sequence-Number: 1587 Kevin Quinlan wrote: > > Are there any good techniques that estimate the time it will take to execute > an SQL statement, specifically an INSERT, SELECT, UPDATE, or DELETE? What > factors are important to consider when estimating the execution time of > these types of SQL statements? > Thank you, > Kevin Complexity and size of statement, complexity and size of tables involved, complexity and size of indices involved, amount of data (if any) returned, RDBM design and implementation consideration, OS, hardware, hardware loading, client design... Really, you need to know what you are trying to acheive. The best way to measure speed is to build a system and populate it with dummy data. Then, analyse your results. - Richard Huxton