Quantcast
Channel: Teradata Developer Exchange - Blog activity for carrie's blog
Viewing all articles
Browse latest Browse all 1058

Elevating Parsing Priority - comment by carrie

$
0
0

Hi Bill,
 
Unfortunately, I don't have any suggestions I can make to improve parsing time on an appliance.  The comments made in my blog posting apply only to sites with TASM and that have defined multiple different workloads for the same WHO criteria.  In SLES 10, the performance group  is determined solely on account string, and you don't have WDIDs.  Both parsing and AMP work will use that same performance group.    I can't think of any way to get around that.
 
You could open an incident with the support center and have them look at specific cases where parsing was unreasonably high and see what they can suggest to you.  Obviously, if you can cache plans by means of parameterized SQL, that can dramatically reduce parsing time.  Sometimes increasing the dictionary cache can eliminate the need to go to the database as often during parsing to get specific dictionary information.   There also may be some DBS Control parameters that could be tuned.  But I am not the right person to attempt to advise you on system-type settings.  
 
Thanks, -Carrie


Viewing all articles
Browse latest Browse all 1058

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>