X-Original-To: pgsql-interfaces@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 7E8F6476300 for ; Fri, 18 Apr 2003 04:29:10 -0400 (EDT) Received: from web13807.mail.yahoo.com (web13807.mail.yahoo.com [216.136.175.17]) by postgresql.org (Postfix) with SMTP id DFAE44762EF for ; Fri, 18 Apr 2003 04:29:01 -0400 (EDT) Message-ID: <20030418082903.61964.qmail@web13807.mail.yahoo.com> Received: from [216.173.173.66] by web13807.mail.yahoo.com via HTTP; Fri, 18 Apr 2003 01:29:03 PDT Date: Fri, 18 Apr 2003 01:29:03 -0700 (PDT) From: Chris Gamache Reply-To: cgg007@yahoo.com Subject: DBD::Pg large processor load. To: pgsql-interfaces@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-5.9 required=5.0 tests=BAYES_01,FROM_ENDS_IN_NUMS version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/137 X-Sequence-Number: 4076 Linux 2.4.20 & PostgreSQL 7.2.3 & DBD::Pg 1.22. I was using PgSQL and PgSQL::Cursor with decent results. However, it is no longer supported, and was causing some problems. So! I switched to DBI. I immediately noticed a jump in processor usage. I primarily use $db->prepare($sql), $rs->execute, and $rs->fetchrow_arrayref. Are there any DBI experts out there with some advice to cut down on processor usage? __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com