Informix and Microstrategy's DSS Agent
Posted in 1999
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BE5AC0.2D7755EE
Content-Type: text/plain;
charset="iso-8859-1"
Hello all,
We are experiencing a problem that maybe someone else has seen before. We
are using Informix 7.22 (I know it's old!) on HP9000 T500 4 way hardware,
HPUX 10.20 os. Our users query this database through Microstrategie's DSS
Agent product. This system has been in place for a couple of years, and
query performance had been pretty poor from the get go, as far as I could
tell when coming onboard a few months back. There was no PDQ being used, so
queries were running for days.
We have made some changes to the client to allow light scans to happen, and
tuned some backend server settings. Now queries are running a lot faster,
and most people are happy. My problem is that users now have very slow
response time when starting the DSS Agent GUI. From what I can tell this
client executes about 25 to 40 small sql statements against a metadata
repository on the Informix server. These login queries are now running with
a pdqprioirty of 10, and if other users are already executing large dss
queries, then they are sitting in the queue. Here are our PDQ settings from
onconfig
MAX_PDQPRIORITY 95
DS_MAX_QUERIES 10
DS_TOTAL_MEMORY 285000
DS_MAX_SCANS 70
I just changed the MAX_PDQPRIORITY from 100 to 95, to allow some resources
for these login activities. That was before I realized that the logins were
using PDQ also. What I am puzzled about is that I can have this system
idle, and kick off an query with pdq of 10 or even 5, and it will take up
100% of the CPU. What else should I be tuning to keep a single query from
monopolizing CPU resources?
Thanks in advance for any suggestions you can provide.
Jeff Screws
jeff.screws@publix.com
------_=_NextPart_001_01BE5AC0.2D7755EE
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>Informix and Microstrategy's DSS Agent</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=3D2 FACE=3D"Arial">Hello all,</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">We are experiencing a problem that =
maybe someone else has seen before. We are using Informix 7.22 (I =
know it's old!) on HP9000 T500 4 way hardware, HPUX 10.20 os. Our =
users query this database through Microstrategie's DSS Agent =
product. This system has been in place for a couple of years, and =
query performance had been pretty poor from the get go, as far as I =
could tell when coming onboard a few months back. There was no =
PDQ being used, so queries were running for days.</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">We have made some changes to the =
client to allow light scans to happen, and tuned some backend server =
settings. Now queries are running a lot faster, and most people =
are happy. My problem is that users now have very slow response =
time when starting the DSS Agent GUI. From what I can tell this =
client executes about 25 to 40 small sql statements against a metadata =
repository on the Informix server. These login queries are now =
running with a pdqprioirty of 10, and if other users are already =
executing large dss queries, then they are sitting in the queue. =
Here are our PDQ settings from onconfig</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">MAX_PDQPRIORITY =
95 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">DS_MAX_QUERIES =
10 &nbs=
p; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">DS_TOTAL_MEMORY =
285000 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">DS_MAX_SCANS 70 =
</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">I just changed the MAX_PDQPRIORITY =
from 100 to 95, to allow some resources for these login =
activities. That was before I realized that the logins were using =
PDQ also. What I am puzzled about is that I can have this system =
idle, and kick off an query with pdq of 10 or even 5, and it will take =
up 100% of the CPU. What else should I be tuning to keep a single =
query from monopolizing CPU resources?</FONT></P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks in advance for any suggestions =
you can provide.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">Jeff Screws</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">jeff.screws@publix.com</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BE5AC0.2D7755EE--