1. Using Progress® Analytical Tools Adam Backman White Star Software adam@wss.com DONE-05:

2. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Outline ä List of available tools ä Using the tools ä Impact of running tools on the system ä Interpreting the data ä Taking action

3. © 2005 White Star Software DONE-05 Using Progress Analytical Tools List of Available Tools ä Progress monitor - promon ä Virtual System Tables - VSTs ä Database Analysis ä Chain analysis ä Index analysis

4. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Using the Tools - promon ä Command line tool promon promon ä Pros: Easy to use Nothing to write Low/no impact on the system ä Cons: No ability to customize No provision to run in batch No provision to output/save data

5. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Using the Tools - VSTs ä 4GL based tool ä Pros: Very customizable Ability to collect exactly what you are looking for Low/no impact on the system ä Cons: You need to write your own tool Determining the right VST is sometimes a challenge

6. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Special Options for Table and Index Statistic VSTs ä All VSTs are on by default but table and index statistics only display the first 50 entries (by number not by volume) ä Use the following options on broker startup -tablebase - The first table number to monitor -tablerangesize - The number of tables to monitor -indexbase - The first index number to monitor -indexrangesize - The number of indexes to monitor

7. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Record Block Summary RECORD BLOCK SUMMARY FOR AREA "Archived Ratings" : 151 Table Records Size Min Max Mean Count Factor Factor PUB.hsrad 68884747 4.0G 53 68 62 68884747 1.0 2.0 PUB.hsrat 353726306 54.1G 120 210 164 353726306 1.0 1.2 -------------------------------------------------------------------------- -------------------------------------------------------------------------- Subtotals: 22611053 58.1G 53 210 147 422611053 1.0 1.4 RECORD BLOCK SUMMARY FOR AREA "Archived Comps" : 152 Table Records Size Min Max Mean Count Factor Factor PUB.hscma 12675 549.7K 43 46 44 12675 1.0 1.5 PUB.hscmd99680152 6.0G 56 99 64 99680152 1.0 1.5 PUB.hscmp41122686 7.0G 98 301 183 41122686 1.0 1.5 PUB.hsgft 9217509 793.0M 67 104 90 9217509 1.0 2.4 ----------------------------------------------------------------------- ----------------------------------------------------------------------- Subtotals: 50033022 13.8G 43 301 98 150033022 1.0 1.6

8. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Index Analysis INDEX BLOCK SUMMARY FOR AREA "Archived Ratings" : 151 ------------------------------------------------------------------------------------- Table Index Fields Levels Blocks Size % Util Factor PUB.hsrad prradstat 18 3 3 4248 21.6M 5.2 1.7 prradstat 18 3 3 4248 21.6M 5.2 1.7 prrat 19 4 3 205141 1.4G 90.3 1.2 prrat 19 4 3 205141 1.4G 90.3 1.2PUB.hsrat audit 13 3 4 397168 3.0G 99.9 1.0 audit 13 3 4 397168 3.0G 99.9 1.0 cmday 14 3 4 421648 2.0G 62.3 1.8 cmday 14 3 4 421648 2.0G 62.3 1.8 cmtbl 45 4 4 1080387 4.2G 50.8 2.0 cmtbl 45 4 4 1080387 4.2G 50.8 2.0 kkcus 15 3 4 842577 4.2G 66.1 1.7 kkcus 15 3 4 842577 4.2G 66.1 1.7 prrat 12 2 4 441148 3.0G 89.0 1.2 prrat 12 2 4 441148 3.0G 89.0 1.2 sltrn 16 3 4 449431 2.9G 85.3 1.3 sltrn 16 3 4 449431 2.9G 85.3 1.3 sylic 17 4 4 471460 3.2G 88.1 1.2 sylic 17 4 4 471460 3.2G 88.1 1.2

9. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Impact of Running the Tools ä The information for both promon and VSTs is kept in memory anyway so the tools are just reading the data with little or no impact to the system ä DB analysis can have an effect on the system especially if you are tightly spec’ed on disk throughput capacity

10. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Interpreting the Data - promon ä What screens to use ä When to use them ä What does the data really mean ä How can I use it to take action

11. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Using promon ä What screen to use: ä Activity screen ä Block access ä When to run ä Beginning of the “day” ä Peak times ä End of the “day”

12. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Activity Screen

13. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Using the Tools - DB analysis ä Command line tool proutil -C dbanalys ä Pros: Only way to determine DB storage efficiency Low impact on the system Can be run while the system is up ä Cons: No historical storage of information No flexibility of output

14. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Example: Block Access

15. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Interpreting the Data - VSTs ä Which VSTs to use ä When to use them ä What does the data really mean ä How can I use the data to take action

16. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Which VSTs to Use ä _TableStat - Table usage ä _IndexStat - Index usage ä _ActSummary - Activity information ä _Transaction - Active transaction listing ä _AreaStatus - Storage area information ä _UserIO - User data request activity

17. © 2005 White Star Software DONE-05 Using Progress Analytical Tools _TableStat ä Displays read, update, create and delete information about each table ä Don’t forget about -tablerangesize ä _TableStat-id = _File._File-Num FOR EACH _TableStat by _TableStat-Read DESCENDING: DISPLAY _TableStat. END.

18. © 2005 White Star Software DONE-05 Using Progress Analytical Tools _IndexStat ä Displays read, update, split and delete information about each index ä Don’t forget about -indexrangesize ä _ IndexStat -id = _Index._Idx-Num FOR EACH _ IndexStat by _ IndexStat -Read DESCENDING: DISPLAY _ IndexStat. END.

19. © 2005 White Star Software DONE-05 Using Progress Analytical Tools _ActSummary ä Akin to the activity screen from promon ä Need to do calculations to get differences ä Two free application (protop and VST dashboard) can show you how this is done. FIND FIRST _ActSummary. DISPLAY _ActSummary.

20. © 2005 White Star Software DONE-05 Using Progress Analytical Tools _Trans ä Good to find “old” transactions ä Could be used to alert the DBA if a transaction duration broke a threshold ä Long running transactions are generally not a good thing as they tend to grow the BI abnormally

21. © 2005 White Star Software DONE-05 Using Progress Analytical Tools _AreaStatus ä This allows you to know how full your areas is while the DB is up and running ä Record contains the total number and number of used (high water) blocks in an area ä If stored over time you could trend your storage and know when you will need to increase capacity in advance

22. © 2005 White Star Software DONE-05 Using Progress Analytical Tools _UserIO ä Total requests by the user ä Most writes should be done by the page writers ä No breakdown as to which tables are being accessed ä Good for initial track down of bad code

23. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Taking Action ä Immediate Action Things that can be changed on the fly ä Planned action Wait for a customary outage and make changes ä Advanced action Trending items to plan for future growth

24. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Immediate Action ä -spin ä Number of APWs ä Application code

25. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Planned Action ä Increasing broker parameters ä Increasing capacity (Disk, memory CPU) ä Changing application code

26. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Advanced Action ä Planning for growth ä Disk storage and throughput capacity ä CPU Utilization ä Memory utilization ä DB storage capacity ä Code efficiency

27. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Interpreting the data - DB analysis ä Should I do a chain analysis, a index analysis or both ä How often should I run the utility ä What does the data really mean ä How can I use it to take action

28. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Conclusion ä Lots of information available ä The utilities included in OpenEdge™ for free are great for a snapshot of how things are now ä For utilities that keep track over time you will need an additional product like Fathom Management or you can write your own

29. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Conclusion Continued ä Use promon to monitor during peak periods of activity or in isolation to determine program efficiency ä VSTs are the basis of Fathom Management and they can be used to determine the reliability and performance data about your database ä DB analysis should be run at least quarterly to determine the efficiency of the indexes ä DB Analysis can also be used to determine storage information for storage area split.

30. © 2005 White Star Software DONE-05 Using Progress Analytical Tools Questions