<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Thanks for the input. I may need just a little more to
put my mind to rest on this, though,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have run similar bench tests before and the results have
always been consistent. This is the first time I have seen them vary.
The only thing I see different in this case, is the Titanium machine and a
little later version of PowerHouse. I am wondering if there is some
tuning that is done on the Titanium machine that is unique to cause this kind
of results. The other possible cause might be that COGNOS has refined QTP
to manage its baggage much better than it used to do. As it is, the
results on the ALPHA are consistent to what I have seen in the
past. It is just on the Titanium that I am seeing such a difference.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>In this case the output file is just a simple subfile.
There are no SORTs, or PARMs. The QUIZ has only GETSYSTEMVALs to make up for
an extract request in the QTP used only to set 3 Global TEMPs and GETSYSEMVALs
are only evaluated once in QUIZ.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>In the past, I have never seen QTP out-perform QUIZ for
simply extracting data and dumping it to a subfile, especially where there is
no totaling or summarizing going included. In this case the data is
getting dumped into a subfile which is then renamed after the extract is complete.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>My understanding is that DEFINES are done in registers while
TEMPs use memory, which easily explains why DEFINEs have to be reevaluated and
TEMPs do not. All things being equal, and no DEFINE cascading, DEFINES
would be faster. Register access much faster than general memory.
It is only when you have multiple references, the cascading, that DEFINEs that
the “fast” DEFINEs have to reevaluate and slow performance.
Register values are only transient.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>QTP, as you say is robust and carries a tremendous amount
flexibility, but with that, come a lot of baggage that is loaded whether it is
used or not. Whereas QUIZ does not carry such a large amount of baggage
and, generally gets through files pretty awful fast by comparison for simple
extracts. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Let me show a little more of my lack of knowledge and ask
what (IMHO) is?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal>John<o:p></o:p></p>
</div>
</body>
</html>