Re: Application bottlenecks

Ideally the odbc driver would log driver time and sql time (optionally) for each statement execution. On windows this would mean rigging up the hardware counter to get accurate timing info. This facility does not exist right now so your best bet is to write a small C test app that interfaces directly with the libpq library and compare latencies with the odbc driver.

You also need to factor in latency from the odbc ISAM wrapper provided by micofocus.

Merlin

________________________________

From: Carlos Henrique Reimer [mailto:carlosreimer(at)yahoo(dot)com(dot)br]
Sent: Thursday, September 08, 2005 12:50 PM
To: Merlin Moncure
Subject: Re: [ODBC] Application bottlenecks

Merlin,

This will be very usefull. But we have a deadline and I´m not sure how much time we can wait. We must propose something to solve the worst cases at least.

But before that, I would like to be sure that our problem is the ODBC driver. Do you know how can I measure the ODBC overhead in our application?

Did you have similar problems?

Thanks,

Reimer

Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> escreveu:
> Hi Merlin...
>
> We have an application that he uses one extfh that was modified by us
> so that it has access Oracle bases natively through the use of
> ProCobol. I am interested in its work, would like to get greaters
> information.
>
> We use Microfocus NetExpress 3.0.
>
> Cleber.
>
> 2005/9/8, Merlin Moncure :
> > Hi Carlos, I am working on project right now you might be interested
in,
> namely a extfh interface to postgresql and a isam wrapper for libpq.
I
> already have an isam bridge working direct to postgresql from AcuCobol
> without using odbc or a commercial driver. I just need to convert it
to
> extfh and do a few other things to support microfocus.
> >
> > Merlin

I have a project open on gborg called 'postisam'. Right now there is no
code and no information on it...but right now I am developing a COBOL
ERP which works with postgresql and AcuCobol. The reason why there is
no public code is that the AcuCobol file interface requires re-linking
the runtime and AcuCorp does not grant redistribution rights on the key
header files required to do that.

With version 7.0 AcuCorp now supports extfh file interfaces so I will
convert my current project to support extfh. In theory, this will allow
postisam to support any cobol compiler that supports extfh. Over the
next couple of weeks I am going to be updating the PostISAM site with
new information and sending in the code that was been reworked with all
the AcuCorp stuff removed and made more portable.

Merlin



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
________________________________

Yahoo! Messenger com voz: PROMOÇÃO VOCÊ PODE LEVAR UMA VIAGEM NA CONVERSA. Participe! <http://us.rd.yahoo.com/mail/br/taglines/*http:/br.yahoo.com/messenger/promocao/>