Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Tom Girsch asked whether IDS 10 servers using only onsoctcp (TCP) listeners on AIX should run poll threads on CPU VPs instead of NET VPs. Keith Simmons said TCP should always be on NET VPs and SHM on CPU VPs. Tom asked if that holds with no SHM at all. David replied that a shared memory listener is still needed because some commands use it. No definitive answer.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Tom Girsch — — source: Usenet: comp.databases.informix
Hello, all. We're in the process of setting up several new IDS 10
servers which will run TCP/IP listeners (onsoctcp on AIX) _only_. In
the past, we've set up shared memory (onipcshm) poll threads to run on
CPU VPs, with the TCP/IP poll threads running on NET VPs. Since the new
servers are running TCP exclusively, with no SHM at all, we're toying
with the idea of running the TCP listeners on the CPU VPs. But a
zillion versions ago (probably 9.21 or maybe even 7.32), doing this
caused problems.
Does anyone have any strong preferences one way or the other? Pros? Cons?
Any feedback is appreciated.
Thanks,
- Tom Girsch
Hilton Hotels
↪ replying to Tom Girsch
Keith Simmons — — source: Usenet: comp.databases.informix
On 04/04/07, Tom Girsch <tgirsch@nospam.gmail.com> wrote:
> Hello, all. We're in the process of setting up several new IDS 10
> servers which will run TCP/IP listeners (onsoctcp on AIX) _only_. In
> the past, we've set up shared memory (onipcshm) poll threads to run on
> CPU VPs, with the TCP/IP poll threads running on NET VPs. Since the new
> servers are running TCP exclusively, with no SHM at all, we're toying
> with the idea of running the TCP listeners on the CPU VPs. But a
> zillion versions ago (probably 9.21 or maybe even 7.32), doing this
> caused problems.
>
> Does anyone have any strong preferences one way or the other? Pros? Cons?
>
> Any feedback is appreciated.
>
> Thanks,
>
> - Tom Girsch
> Hilton Hotels
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
Tom
TCP connections should always be run on NET VPs and SHM on CPU. There
are many threads on this from about 2002/3 explaining exactly why and
how performance will plummet if you mix them up !!
Keith
↪ replying to Keith Simmons
Tom Girsch — — source: Usenet: comp.databases.informix
Keith Simmons wrote:
> Tom
>
> TCP connections should always be run on NET VPs and SHM on CPU. There
> are many threads on this from about 2002/3 explaining exactly why and
> how performance will plummet if you mix them up !!
>
I just want to verify that this still applies even when you're not
running SHM listeners at all. We'll be running ONLY TCP listeners.
On 5 Apr, 00:10, Tom Girsch <tgir...@NOSPAM.gmail.com> wrote:
> Keith Simmons wrote:
> > Tom
>
> > TCP connections should always be run on NET VPs and SHM on CPU. There
> > are many threads on this from about 2002/3 explaining exactly why and
> > how performance will plummet if you mix them up !!
>
> I just want to verify that this still applies even when you're not
> running SHM listeners at all. We'll be running ONLY TCP listeners.
I believe you need shm listeners as some commands reply on a shm
listener.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.