I run the ODBC server in the EQ with the following queue setting for it.

tune eq=170,220,300,300,oscillate

This works just swimingly (I've always wanted to say that).  Actually since
 the system we built has 99% of the connections coming in this way, they
are contending for
the same CPU anyway.





Jim Phillips <[log in to unmask]> on 01/21/2000 06:19:45 AM

Please respond to Jim Phillips <[log in to unmask]>



 To:      [log in to unmask]

 cc:      (bcc: Shawn Gordon/IS/FHM/FHS)



 Subject: Re: Data-Exchange with HP3000







Shawn Gordon <[log in to unmask]> writes:

> ODBC is actually pretty effecient, at least the one from MiniSoft which
is
> where my experience is.  The server parses down the data you need and
then
> passes it down, as opposed to passing everything down and having you
> program figure out what to use.  If you want to write custom servers then
> you could get one of the various middleware packages available and write
> your own servers to maximize performance.

My experience is limited to one (other) ODBC software.  But I have found
that it desires as much memory as you can provide and the listener must be
in the CS queue in order to service the requests in a timely manner.  Thus
you get a lot of CPU usage.  You can restrict the CPU usage by dropping the
listener into the DS queue, but then you have timeout problems.

Like most performance tuning, it's a trade-off....

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]     Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231