[Info-Ingres] iigcc takes over the computer

[BruceL]

On Oct 29, 5:24 am, Allan Biggs <Allan.Bi... at GBR.dupont.com> wrote:
> I have asked this question before some time ago - but just in case anyone
> didn't see it and knows how to get around this
>
> I am connecting to an ingres database via the internet (over VPN).
>
> I notice that iigcc.exe takes up to 90 + percent of the cpu when any
> application is connected to a database.
>
> I have set II_WINSOCK_SELECT=1000000.
>
> I have validated that when connected directly to a LAN iigcc behaves as
> expected using CPU as required.
>
> thanks to anyone who knows how to cure this.
>
> Allan
>
> This communication is for use by the intended recipient and contains
> information that may be Privileged, confidential or copyrighted under
> applicable law. If you are not the intended recipient, you are hereby
> formally notified that any use, copying or distribution of this e-mail,
> in whole or in part, is strictly prohibited. Please notify the sender by
> return e-mail and delete this e-mail from your system. Unless explicitly
> and conspicuously designated as "E-Contract Intended", this e-mail does
> not constitute a contract offer, a contract amendment, or an acceptance
> of a contract offer. This e-mail does not constitute a consent to the
> use of sender's contact information for direct marketing purposes or for
> transfers of data to third parties.
>
> Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean
>
>            http://www.DuPont.com/corp/email_disclaimer.html

I used to see this on Win 95 and Win 98 machines (with or without a
VPN), but not on Win NT, 2000, or XP.  The cause of that problem was
the frequent polling in the Ingres Winsock protocol driver.  However,
it seemed to be a low priority usage of the CPU because it did not
affect performance.  On Windows NT/2000/XP, the code is the same, but
the OS did not report the high CPU utilization.  What version of
Windows and Ingres are you running?   Although there has never been a
specific fix for the problem that you are noticing, there were some
fixes (bugs 106589 and 110337) which greatly improved performance in
the winsock polling code area.  Prior to these fixes, increasing the
II_WINSOCK_SELECT value too high would reduce the CPU utilization, but
kill performance.  After the fixes, II_WINSOCK_SELECT could be set
high without affecting performance.

In your case, you state that the problem only occurs across your VPN.
I've never heard of that before and, in fact, just tried it on our VPN
and it did not demonstrate the problem.  We happen to use the CISCO
VPN software.  I tried it using Ingres 2.6 on both ends, but not sure
what release you're at.

If using Ingres r3 or later, try using the "tcp_ip" protocol driver
instead of "wintcp".  The "tcp_ip" protocol driver is newer and uses
the Winsock2 API/protocol instead of the original Winsock.  Switching
involves modifying your vnode definition and your Ingres/Net protocol
driver via CBF or similar config utility.

Regards,

Bruce