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.
Hello my friends.
(Informix 11.70.FC2 on a linux_64 machine)
I had configured our PDQ features (since 11.50) like this (onstat -g mgm
output):
Memory Grant Manager (MGM)
--------------------------
MAX_PDQPRIORITY: 80
DS_MAX_QUERIES: 40
DS_MAX_SCANS: 1048576
DS_NONPDQ_QUERY_MEM: 75000 KB
DS_TOTAL_MEMORY: 3145728 KB
For one specific user, I´ve adjusted the new parameters like this (sysdbopen):
SET PDQPRIORITY 30;
SET ENVIRONMENT IMPLICIT_PDQ ON;
SET ENVIRONMENT BOUND_IMPL_PDQ ON;
I have (now) only one session on "Active Queries" section:
Session Query Priority Thread Memory Scans Gate
42782 1730d2438 32 16a3c59e0 0/0 1/1 -
And the others are all incoming into "Ready Queries" section:
Ready Queries:
--------------
Session Query Priority Thread Memory Scans Gate
46543 1692fc038 32 15a8eb3a8 0/125824 0/0 5
46226 15abd0ae8 24 15ab725d8 0/0 0/1 5
My question is: shouldn´t the engine automatically low the active pdq, and
include the other two queries on the active section (instead of letting them
stalled in ready section)?
From the official docs, I´ve read the "upper limit" would be 30 (in my case),
and the engine should arrange from available resources, respecting my
DS_MAX_QUERIES limit, shouldn´t it?
Regards.
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.