Thanks for the reply. I'll be putting up a data warehouse later this year
so I was attempting to test the impact of intra-parallel against all of my
existing load tests. Do you have any ideas?
-----Original Message-----
From: DANIEL CALLAHAN [mailto:[Email address protected]
Sent: Wednesday, October 27, 2004 8:49 AM
To: [Email address protected]
Subject: Re: Parallel Queries
**A LazyDBA.com subscriber has responded to your lazydba.com post**
**LazyDBA.com mail shield has forwarded you this email,
**and removed any attachments, and kept your email address secret
**from this person, and any viruses/trojans.
**If you reply to this email, the person will see your email address as
normal
**Anything below this line is the original email text
What kind of processing are you doing? Intra-parallel should be turned on
with DPF enviroments for extremely complex queries.
it might not be applicable to your environment.
Dan Callahan IT Specialist
603-472-4121 t/l 525-4121
[Email address protected]
[Email address protected]
"Blair Jensen "
<db2udbdba-ezmlms
hield-x23016339.x To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
10/27/2004 11:32
AM Subject
Parallel Queries
I've got a new 4 CPU server and turned on INTRA_PARALLEL with 1700
maxagents, 400 maxappls, and query degree of 4. I expected that no more
than 1600 agents would be spawned (4 query degree * 400 max applications).
However, in a simple load test of 350 connections executing a query every 5
seconds I eventually run over 1700 agents. I've included some snapshot
information as well as my config statements. Any help would be
appreciated.
Thanks,
Blair Jensen
High water mark for connections = 346
Application connects = 1035
Secondary connects total = 0
Applications connected currently = 690
Appls. executing in db manager currently = 320
Agents associated with applications = 1700
Maximum agents associated with applications= 1701
Maximum coordinating agents = 346
Remote connections to db manager = 348
Remote connections executing in db manager = 1
Local connections = 1
Local connections executing in db manager = 0
Active local databases = 1
High water mark for agents registered = 1702
High water mark for agents waiting for a token = 0
Agents registered = 1701
Agents waiting for a token = 0
Idle agents = 0
Agents assigned from pool = 340
Agents created from empty pool = 1717
Agents stolen from another application = 28
High water mark for coordinating agents = 350
Max agents overflow = 0
db2 UPDATE DATABASE MANAGER CONFIGURATION USING MAXAGENTS 1700
db2 UPDATE DATABASE MANAGER CONFIGURATION USING INTRA_PARALLEL ON
db2 UPDATE DATABASE MANAGER CONFIGURATION USING MAX_QUERYDEGREE 4
db2 UPDATE DATABASE CONFIGURATION FOR PECP USING MAXAPPLS 400
db2 UPDATE DATABASE CONFIGURATION FOR PECP USING DFT_DEGREE 4
"Attention: This message is intended only for the individual to whom it is
addressed and may contain information that is confidential or privileged.
If
you are not the intended recipient, or the employee or person responsible
for
delivering it to the intended recipient, you are hereby notified that any
dissemination, distribution, copying or use is strictly prohibited. If you
have received this communication in error, please notify the sender and
destroy or delete this communication immediately."
============================================================================
==
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page