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.
Jason Ball asked about the impact of too few connections per thread with NETTYPE ipcstr,12,200,CPU. Art Kagel said the setting is per listener, connections auto-expand, and responsiveness only suffers above roughly 500-700 active connections per listener. Jason concluded 5000 user threads would be adequately covered. Resolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Jason Ball — source: IBM Community (ConnectedCommunity.org) Informix forum
Hi all
What is the impact of not having enough threads per connection.
NETTYPE ipcstr,12,200,CPU
VPCLASS cpu,num=12,noage,autotune=1,max=14.How do I know if I am getting up towards that limit.
Regards
Jason
------------------------------
Jason Ball
------------------------------
#Informix
↪ replying to Jason Ball
Art Kagel — source: IBM Community (ConnectedCommunity.org) Informix forum
Keeping in mind that the number of connections is auto-expanding, and also my other notes from your previous post/question, if you approach or surpass the efficiency zone (500-700 active connections per listener), responsiveness to user requests will seem to be slow although once a request is picked up the response should be quick as usual.
The keyword here is "active" connections. If you have 9000 users connected but only 300 of them are actively submitting requests (new queries or even just "next block of data" requests) then you will still be OK.
------------------------------
Art S. Kagel, President and Principal Consultant
ASK Database Management Corp.
www.askdbmgt.com
------------------------------
↪ replying to Art Kagel
Jason Ball — source: IBM Community (ConnectedCommunity.org) Informix forum
Thanks Art. My apologies for double posting, The first one was submitted Friday, but I didn't see it on lists on Monday, so thought I must have made an error. I will be more patient next time.
Just to be very clear, even though the config is about specifying connections per thread, performance is more affected by _active_ connections per _listener_? What do we need to consider in the "number of connections per thread" then?
------------------------------
Jason Ball
------------------------------
↪ replying to Jason Ball
Jason Ball — source: IBM Community (ConnectedCommunity.org) Informix forum
Hmm, I think I'm getting threads and listeners tangled up. The config is about connections per listener, performance is not affected below 500-700 connections per listener. Per your reply on my other post, the engine will increase the number of connections as required (except for shared memory types).
So 5000 user threads will be adequately covered by this configuration, especially when considering the active user threads are a fraction of this.
------------------------------
Jason Ball
------------------------------
Your privacy choices
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.