| From: | Rudy Lippan <rlippan(at)remotelinux(dot)com> |
|---|---|
| To: | Chris Gamache <cgg007(at)yahoo(dot)com> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: DBD::Pg large processor load. |
| Date: | 2003-04-21 18:43:23 |
| Message-ID: | Pine.LNX.4.44.0304211440000.4221-100000@elfride.ineffable.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Fri, 18 Apr 2003, Chris Gamache wrote:
> 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?
>
How much of a processor load are you talking about? Is it a 2%, 20%, 200%
increase in processor usage?
1. Does PgSQL::Cursor uses Cursors?
2. Do you have code that shows the problem?
-r
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rise | 2003-04-22 01:21:11 | Re: [INTERFACES] Speed of SSL connections; cost of |
| Previous Message | Glenn R Williams | 2003-04-21 18:10:08 | pl/python exceptions.ImportError: No module named _sre |