using progress® analytical tools adam backman white star software done-05:

Using Progress®Analytical Tools

Adam BackmanAdam BackmanWhite Star SoftwareWhite Star Software

[email protected]@wss.com

DONE-05:DONE-05:

DONE-05 Using Progress Analytical ToolsDONE-05 Using Progress Analytical Tools © 2005 White Star Software© 2005 White Star Software

Outline

List of available toolsList of available tools Using the toolsUsing the tools Impact of running tools on the systemImpact of running tools on the system Interpreting the dataInterpreting the data Taking actionTaking action


List of Available Tools

Progress monitor - promonProgress monitor - promon Virtual System Tables - VSTsVirtual System Tables - VSTs Database AnalysisDatabase Analysis

Chain analysisChain analysis Index analysisIndex analysis


Using the Tools - promon

Command line toolCommand line toolpromon <dbname>promon <dbname>

Pros:Pros:Easy to useEasy to useNothing to writeNothing to writeLow/no impact on the systemLow/no impact on the system

Cons:Cons:No ability to customizeNo ability to customizeNo provision to run in batchNo provision to run in batchNo provision to output/save dataNo provision to output/save data


Using the Tools - VSTs

4GL based tool4GL based tool Pros:Pros:

Very customizableVery customizableAbility to collect exactly what you are looking forAbility to collect exactly what you are looking forLow/no impact on the systemLow/no impact on the system

Cons:Cons:You need to write your own toolYou need to write your own toolDetermining the right VST is sometimes a challengeDetermining the right VST is sometimes a challenge


Special Options for Table and Index Statistic VSTs

All VSTs are on by default but table and index All VSTs are on by default but table and index statistics only display the first 50 entries (by statistics only display the first 50 entries (by number not by volume)number not by volume)

Use the following options on broker startupUse the following options on broker startup-tablebase - The first table number to monitor-tablebase - The first table number to monitor-tablerangesize - The number of tables to monitor -tablerangesize - The number of tables to monitor -indexbase - The first index number to monitor-indexbase - The first index number to monitor-indexrangesize - The number of indexes to monitor -indexrangesize - The number of indexes to monitor


Example: Record Block Summary

RECORD BLOCK SUMMARY FOR AREA "Archived Ratings" : 151RECORD BLOCK SUMMARY FOR AREA "Archived Ratings" : 151

Table Table Records Size Min Max Mean Count Factor Factor Records Size Min Max Mean Count Factor FactorPUB.hsrad PUB.hsrad 68884747 4.0G 53 68 62 68884747 1.0 2.068884747 4.0G 53 68 62 68884747 1.0 2.0PUB.hsrat PUB.hsrat 353726306 54.1G 120 210 164 353726306 1.0 1.2353726306 54.1G 120 210 164 353726306 1.0 1.2 ----------------------------------------------------------------------------------------------------------------------------------------------------Subtotals: Subtotals: 22611053 58.1G 53 210 147 422611053 1.0 1.422611053 58.1G 53 210 147 422611053 1.0 1.4

RECORD BLOCK SUMMARY FOR AREA "Archived Comps" : 152RECORD BLOCK SUMMARY FOR AREA "Archived Comps" : 152

Table Table Records Size Min Max Mean Count Factor FactorRecords Size Min Max Mean Count Factor FactorPUB.hscmaPUB.hscma 12675 549.7K 43 46 44 12675 1.0 1.5 12675 549.7K 43 46 44 12675 1.0 1.5PUB.hscmdPUB.hscmd 99680152 6.0G 56 99 64 99680152 1.0 1.599680152 6.0G 56 99 64 99680152 1.0 1.5PUB.hscmpPUB.hscmp 41122686 7.0G 98 301 183 41122686 1.0 1.541122686 7.0G 98 301 183 41122686 1.0 1.5PUB.hsgftPUB.hsgft 9217509 793.0M 67 104 90 9217509 1.0 2.4 9217509 793.0M 67 104 90 9217509 1.0 2.4 ----------------------------------------------------------------------------------------------------------------------------------------------Subtotals: Subtotals: 50033022 13.8G 43 301 98 150033022 1.0 1.650033022 13.8G 43 301 98 150033022 1.0 1.6


Example: Index Analysis

INDEX BLOCK SUMMARY FOR AREA "Archived Ratings" : 151INDEX BLOCK SUMMARY FOR AREA "Archived Ratings" : 151

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Table Index Fields Levels Blocks Size % Util FactorTable Index Fields Levels Blocks Size % Util Factor

PUB.hsradPUB.hsrad prradstat 18 prradstat 18 3 3 4248 21.6M 5.2 1.7 3 3 4248 21.6M 5.2 1.7 prrat 19 prrat 19 4 3 205141 1.4G 90.3 1.2 4 3 205141 1.4G 90.3 1.2PUB.hsratPUB.hsrat audit 13 audit 13 3 4 397168 3.0G 99.9 1.0 3 4 397168 3.0G 99.9 1.0 cmday 14 cmday 14 3 4 421648 2.0G 62.3 1.8 3 4 421648 2.0G 62.3 1.8 cmtbl 45 cmtbl 45 4 4 1080387 4.2G 50.8 2.0 4 4 1080387 4.2G 50.8 2.0 kkcus 15 kkcus 15 3 4 842577 4.2G 66.1 1.7 3 4 842577 4.2G 66.1 1.7 prrat 12 prrat 12 2 4 441148 3.0G 89.0 1.2 2 4 441148 3.0G 89.0 1.2 sltrn 16 sltrn 16 3 4 449431 2.9G 85.3 1.3 3 4 449431 2.9G 85.3 1.3 sylic 17 sylic 17 4 4 471460 3.2G 88.1 1.2 4 4 471460 3.2G 88.1 1.2


Impact of Running the Tools

The information for both promon and VSTs The information for both promon and VSTs is kept in memory anyway so the tools are is kept in memory anyway so the tools are just reading the data with little or no impact just reading the data with little or no impact to the systemto the system

DB analysis can have an effect on the DB analysis can have an effect on the system especially if you are tightly spec’ed system especially if you are tightly spec’ed on disk throughput capacityon disk throughput capacity


Interpreting the Data - promon

What screens to useWhat screens to use When to use themWhen to use them What does the data really meanWhat does the data really mean How can I use it to take actionHow can I use it to take action


Using promon

What screen to use:What screen to use: Activity screenActivity screen Block accessBlock access

When to runWhen to run Beginning of the “day”Beginning of the “day” Peak timesPeak times End of the “day”End of the “day”


Example: Activity Screen


Using the Tools - DB analysis

Command line toolCommand line toolproutil <dbname> -C dbanalysproutil <dbname> -C dbanalys

Pros:Pros:Only way to determine DB storage efficiencyOnly way to determine DB storage efficiencyLow impact on the systemLow impact on the systemCan be run while the system is upCan be run while the system is up

Cons:Cons:No historical storage of informationNo historical storage of informationNo flexibility of outputNo flexibility of output


Example: Block Access


Interpreting the Data - VSTs

Which VSTs to useWhich VSTs to use When to use themWhen to use them What does the data really meanWhat does the data really mean How can I use the data to take actionHow can I use the data to take action


Which VSTs to Use

_TableStat - Table usage_TableStat - Table usage _IndexStat - Index usage_IndexStat - Index usage _ActSummary - Activity information_ActSummary - Activity information _Transaction - Active transaction listing_Transaction - Active transaction listing _AreaStatus - Storage area information_AreaStatus - Storage area information _UserIO - User data request activity_UserIO - User data request activity


_TableStat

Displays read, update, create and delete Displays read, update, create and delete information about each tableinformation about each table

Don’t forget about -tablerangesizeDon’t forget about -tablerangesize _TableStat-id = _File._File-Num_TableStat-id = _File._File-NumFOR EACH _TableStat FOR EACH _TableStat

by _TableStat-Read DESCENDING:by _TableStat-Read DESCENDING:DISPLAY _TableStat.DISPLAY _TableStat.

END.END.


_IndexStat

Displays read, update, split and delete information Displays read, update, split and delete information about each indexabout each index

Don’t forget about -indexrangesizeDon’t forget about -indexrangesize _ _ IndexStatIndexStat-id = _Index._Idx-Num-id = _Index._Idx-NumFOR EACH _FOR EACH _IndexStatIndexStat

by _by _IndexStatIndexStat-Read DESCENDING:-Read DESCENDING:DISPLAY _DISPLAY _IndexStatIndexStat..

END.END.


_ActSummary

Akin to the activity screen from promonAkin to the activity screen from promon Need to do calculations to get differencesNeed to do calculations to get differences Two free application (protop and VST Two free application (protop and VST

dashboard) can show you how this is done. dashboard) can show you how this is done. FIND FIRST _ActSummary.FIND FIRST _ActSummary.DISPLAY _ActSummary.DISPLAY _ActSummary.


_Trans

Good to find “old” transactionsGood to find “old” transactions Could be used to alert the DBA if a Could be used to alert the DBA if a

transaction duration broke a thresholdtransaction duration broke a threshold Long running transactions are generally not Long running transactions are generally not

a good thing as they tend to grow the BI a good thing as they tend to grow the BI abnormallyabnormally


_AreaStatus

This allows you to know how full your This allows you to know how full your areas is while the DB is up and runningareas is while the DB is up and running

Record contains the total number and Record contains the total number and number of used (high water) blocks in an number of used (high water) blocks in an area area

If stored over time you could trend your If stored over time you could trend your storage and know when you will need to storage and know when you will need to increase capacity in advanceincrease capacity in advance


_UserIO

Total requests by the userTotal requests by the user Most writes should be done by the page Most writes should be done by the page

writerswriters No breakdown as to which tables are being No breakdown as to which tables are being

accessedaccessed Good for initial track down of bad codeGood for initial track down of bad code


Taking Action

Immediate Action Immediate Action Things that can be changed on the flyThings that can be changed on the fly

Planned action Planned action Wait for a customary outage and make changesWait for a customary outage and make changes

Advanced actionAdvanced actionTrending items to plan for future growthTrending items to plan for future growth


Immediate Action

-spin-spin Number of APWsNumber of APWs Application codeApplication code


Planned Action

Increasing broker parametersIncreasing broker parameters Increasing capacity (Disk, memory CPU)Increasing capacity (Disk, memory CPU) Changing application codeChanging application code


Advanced Action

Planning for growthPlanning for growth Disk storage and throughput capacityDisk storage and throughput capacity CPU UtilizationCPU Utilization Memory utilizationMemory utilization

DB storage capacityDB storage capacity Code efficiencyCode efficiency


Interpreting the data - DB analysis

Should I do a chain analysis, a index Should I do a chain analysis, a index analysis or bothanalysis or both

How often should I run the utilityHow often should I run the utility What does the data really meanWhat does the data really mean How can I use it to take actionHow can I use it to take action


Conclusion

Lots of information availableLots of information available The utilities included in OpenEdgeThe utilities included in OpenEdge™™ for for

free are great for a snapshot of how things free are great for a snapshot of how things are noware now

For utilities that keep track over time you For utilities that keep track over time you will need an additional product like Fathom will need an additional product like Fathom Management or you can write your ownManagement or you can write your own


Conclusion Continued

Use promon to monitor during peak periods of Use promon to monitor during peak periods of activity or in isolation to determine program activity or in isolation to determine program efficiencyefficiency

VSTs are the basis of Fathom Management and VSTs are the basis of Fathom Management and they can be used to determine the reliability and they can be used to determine the reliability and performance data about your databaseperformance data about your database

DB analysis should be run at least quarterly to DB analysis should be run at least quarterly to determine the efficiency of the indexesdetermine the efficiency of the indexes

DB Analysis can also be used to determine storage DB Analysis can also be used to determine storage information for storage area split.information for storage area split.


Questions

using progress® analytical tools adam backman white star software done-05:

Documents