Dear Gerardo,
Perl + DBI + DBD::Informix imposes at least a moderate amount of overhead
compared with a raw ESQL/C program. Whether the time ratio you are seeing is
reasonable is slightly more debatable, but I would expect the Perl
combination to be slower. The big question for you is "is it too slow?" And
there's a subsidiary question - if you decide the answer is "yes; it is too
slow", then "is it cost-effective to write the application in ESQL/C
instead?"
The other alternative is that you do the analysis and demonstrate where the
DBD::Informix code is unnecessarily slow (profiling, etc), and you suggest
ways to fix it. Patches are always welcome!
On 7/3/05, Gerardo Santana Gómez Garrido <[EMAIL PROTECTED]> wrote:
>
> ---------- Forwarded message ----------
> From: Gerardo Santana Gómez Garrido <[EMAIL PROTECTED]>
> Date: Jun 29, 2005 1:46 PM
> Subject: it works, but...
> To: [EMAIL PROTECTED]
>
>
> I'm sending you attached the output of it_works.
>
> DBD::Informix works fine, except that it's taking twice the time than
> ESQL/C when I SELECT from a table and do a while($ref = $stmt->fetch)
> { }
>
> This table has aprox. 250 fields and 8000 rows. It takes 199 seconds
> for perl to execute the select and fetch all the records, while for
> the program in ESQL/C (that selects, fetch, aggregates and prints a
> report) it takes 72 seconds.
>
> Any ideas?
>
> --
> Gerardo Santana Gómez Garrido
> http://www.openbsd.org.mx/santana/
> "Entre los individuos, como entre las naciones, el respeto al derecho
> ajeno es la paz" -Don Benito Juárez
>
>
>
--
Jonathan Leffler <[EMAIL PROTECTED]> #include <disclaimer.h>
Guardian of DBD::Informix - v2005.01 - http://dbi.perl.org
"I don't suffer from insanity - I enjoy every minute of it."
