↧
Channel:
Teradata Developer Exchange - Blog activity for carrie's blog
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: Teradata Developer Exchange - Blog activity for carrie's blog
- Channel Number: 4274858
- Language: English
- Registered On: September 10, 2012, 9:21 pm
- Number of Articles: 1058
- Latest Snapshot: June 6, 2019, 4:01 am
- RSS URL: http://developer.teradata.com/blog/carrie/rss.xml
- Publisher: http://downloads.teradata.com/blog/carrie
- Description:
- Catalog: //teradata138.rssing.com/catalog.php?indx=4274858
© 2025 //www.rssing.com
Hi Carrie,
we recently migrated to 6800 system and implemented PMCOD 75% .
I am using following formulae for available CPU Cycles in 6800 system.
So estimated total available CPU seconds/day is #Nodes*#CPUs*Seconds/day = 4*32*86,400 CPU Seconds/day . i.e. 11,059,200 CPU Seconds/day.
As per my understanding, 75% PMCOD means CPU will theoretically be 33% higher compared to no COD. It is nothing but, the access to CPU is reduced by internal mechanisms that stop the CPU from doing work for a percent of the time for each core on the node. So CPU Utilization recorded in DBQL will be higher by an amount that represents the inverse of the PMCOD level.
So bottom line is, the total available CPU cycles/day won’t change but with COD, CPU utilization by the user will be higher as compared to no COD.
Is my understanding correct or is it little more complicated?