Benchmark Macro %COMPARE Sreekanth Reddy Middela, MaxisIT Inc., Edison, NJ Venkata Sekhar Bhamidipati, Merck & Co., Inc.

Transcription

1 Benchmark Macro %COMPARE Sreekanth Reddy Middela, MaxisIT Inc., Edison, NJ Venkata Sekhar Bhamidipati, Merck & Co., Inc., North Wales, PA ABSTRACT The main functionality of benchmark macro %Compare is to summarize, aggregate, and display the various hardware resources utilized by a SAS program. Additionally, %Compare compares, between two programs, resources such as memory, real time, CPU time, etc., which is a useful benchmarking technique to help determine the program structure and hardware needs. %Compare can be helpful for programmers working on large databases such as those occurring with vaccine clinical trials or sales data. This paper will illustrate techniques using various real scenarios. INTRODUCTION This paper examines a few of the most common questions regarding efficient SAS code. Its main focus is to examine the usage of overall memory, real time, and CPU time differences between two programs/logs. Except where noted, all examples were tested in production versions of SAS on Windows XP platforms. %Compare is user friendly with a display window for inputs as well as a PDF display for outputs. It is important to understand that the memory, real times, and CPU times shown in the logs in this paper are not necessarily indicative of the times you may see if you try the same tests. These times vary greatly between operating systems and between machine configurations. The times used here are primarily for purposes of comparison to help you to make decisions and improve on SAS coding practices. In addition to comparing two program resources %Compare identifies the data or proc steps in which the system is not moving data well. Additionally, this macro produces summary statistics tables for each step by group. MACRO DESIGN The main objective of %Compare is to compare two SAS programs/logs and determine which is more efficient in using a minimum amount of CPU time. It identifies the data or proc steps in which the system is not moving the data well. The macro shows techniques to read information from log files, and has a user friendly pop-up window for input and a PDF output. Performance %Compare is designed to gauge the efficiency between two SAS programs in a new way which is by measuring the total CPU resource utilized to execute SAS programs. If a SAS program with many data and proc steps uses a huge amount of resources, it is often difficult to determine which data and proc steps are using most of the resources. %Compare identifies some of the steps which may be using most resources. According to the SAS user manual, "If the real time and total CPU time are within 15 percent of each other, this usually indicates that the system is moving data well (at least during the run time of that job/step processing)." This means that the ratio of CPU processing time is close to that of the total job. Based on this information, %Compare identifies the steps where the real time and total CPU time are not within 15 percent of each other. Reading information from log files One of the main challenges of the macro is to read the log file which can be huge and not user friendly and difficult to review manually. There are several ways to read the log to identify each data or proc step and their associated resources (i.e. real time and CPU time etc.); %Compare uses the "indexw" function to do that. User friendly input/output One of the best features of %Compare is user friendly input and output in that it accepts the input through a popup window. The user can enter SAS program or SAS log names, and the output is in the form of a user friendly PDF. 1

2 Flow chart Two SAS programs Or Two SAS logs Through a user friendly window Log inputs Program Execute programs with FULLSTIMER option and produce log Conclusion Overall resources utilization Table Read logs for real time, CPU time Execute etc.. and program perform and produce log summary statistics Steps in which real time and total CPU time are not within 15 percent to each other Summary statistics for each step Outputs User friendly input from a pop-up window screen %Compare accepts either two programs or two logs as input. The SAS code below creates a pop-up window which accepts input and stores the values in "pgmx1" and "pgmx2" %window ram icolumn=60 irow=20 columns=60 rows=40 color = black #15 'Please Enter the 1st Program/Log Name:' color = white pgmx1 20 Display=YES REQUIRED=YES ATTR=UNDERLINE color=white #16 'Please Enter the 2nd Program/Log Name:' color = white pgmx2 20 Display=YES REQUIRED=YES ATTR=UNDERLINE color= white 'Press Enter to continue.' color= white ; %display ram bell delete; 2

3 Below is the snap shot of the pop-up window screen to accept input The SAS code below concatenates the stored input variables "pgmx1" and "pgmx2" from the pop-up window to the name of the library where the programs or logs reside. It then identifies whether the inputs are programs or logs (using %if %index(&pgm1,.log) eq 0). If the inputs are programs, the "%creatlog" macro includes the FULLSTIMER option in programs providing additional system resource information (i.e. memory, system CPU resources), and executes programs. It then produces the log files. If the inputs are logs the macro goes to the next step of reading logs and identifying system resources such as real time, CPU time, etc. %let pgmdir = C:\ram ; /* Library where your programs reside */ %let pgm1=&pgmdir\&pgmx1; %let pgm2=&pgmdir\&pgmx2; %if %index(&pgm1,.log) eq 0 %then %createlog(num = 1) ; /* %creatlog macro execute programs and produces log */ %else filename pgm1 "&pgm1"; Capturing system resources like memory, CPU time, etc. This is one of the main sections of the macro. It captures all the resources like real time, CPU time, etc. using the "indexw" function. %Compare works for logs that are not using FULLSTIMER option and for programs which use FULLSTIMER option. The flag "&logflag" indicates whether it is a log or a program. Based on the flag the macro captures the resources information using the SAS code below: %if &logflag ne 0 %then %do ; /* if the input is a log */ if indexw(name,'real time') or indexw(name,'cpu time' ) then do ; value = input(compress(name,' real cpu time seconds'),8.) ; if indexw(name,'real time' ) then flag = 'real' ; if indexw(name,'cpu time' ) then flag = 'cpu' ; output ; end ; %end ; 3

4 %if &logflag eq 0 %then %do ; /* if the input is a Program */ if indexw(name,'real time' ) or indexw(name,'user cpu time') or indexw(name,'system cpu time') or indexw(name,'memory') then do ; if indexw(name,'real time' ) then flag = 'real' ; if indexw(name,'user cpu time' ) then flag = 'user cpu time' ; if indexw(name,'system cpu time' ) then flag = 'system cpu time' ; if indexw(name,'memory' ) then flag = 'memory' ; value = input(compress(name,' real cpu time seconds Memory k'),8.) ; output ; end ; %end ; Outputs In this final section the captured log information is processed using SAS procedures (like univariate, transpose, report, etc.) and produces the following outputs: 1) A conclusion stating which program/log is using the minimum amount of CPU time. 2) A table with total real times, CPU times and memory utilized for each program/log. 3) The steps in which real time and total CPU time are not within 15 percent of each other. 4) Summary stats tables for all steps by group. Example 1 Comparing two Logs In this example ve1.log and ve2.log are two program logs in which the FULLSTIMER option was not used to produce the logs. 1) Which program log is using minimum amount of resources Comparison of System Resource Utilization Between Two Programs Conclusion ve2.log is using Less CPU resources than ve1.log 2) Total real time and CPU time for both program logs Overall Resources Utilization Table ve1.log ve2.log real time (in Sec) cpu time (in Sec) ) The steps in which real time and total CPU time are not within 15 percent of each other Program Log: ve1.log real cpu DATA DATA Program Log: ve2.log real cpu DATA DATA DATA

5 4) The summary statistics for each type of step Summary Statistics for Each Step Program/log: ' ve1.log' Steps Real Time CPU Time CONTENTS N 1 1 MEAN STD.. SUM MAX MD MIN DATA N MEAN STD SUM MAX MD MIN 0 0 Example 2 Comparing two programs In this example, test_pgm1.sas, test_pgm2.sas are two programs in which the FULLSTIMER option is used to produce these logs by the %Compare macro. 1) Which program is using minimum amount of resources Comparison of System Resource Utilization between two Programs Conclusion test_pgm1.sas is using Less CPU resources than test_pgm2.sas 2) Total real time and CPU time for both program logs Overall Resources Utilization Table test_pgm1.sa s test_pgm2.sa s real time (in Sec) cpu time (in Sec) Memory in Kilo Bytes ) The steps in which real time and total CPU time are not within 15 percent of each other Note: this example did not produce this output because for all the steps the real time and CPU time are within 15 percent of each other. 5

6 4) The summary statistics for each type of step Summary Statistics for Each Step Program/log: ' test_pgm1.sas' Steps Memory Real System CPU Time User CPU Time DATA N MEAN STD SUM MAX MD MIN Summary Statistics for Each Step Program/log: ' test_pgm2.sas System CPU Time User CPU Time Steps Memory Real DATA N MEAN STD SUM MAX MD MIN CONCLUSION After executing this user friendly macro %Compare, the user knows which SAS program is using the minimum CPU time and also knows the data or proc steps in which the system is not moving the data well. This is a useful benchmarking technique to improve the efficiency of a SAS program. The SAS programmer should consider all aspects of the application to make the appropriate choice. REFERENCES: SAS User Guide (link: Su, Y., Glaser, A. The Extraction, Summarization, and Presentation of Information from SAS Log Files. PhilaSUG, November ACKNOWLEDGMENTS SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies. CONTACT INFORMATION Your comments and questions are valued and encouraged. Contact the author at: Sreekanth Reddy Middela Venkata Sekhar Bhamidipati MaxisIT Inc. Merck & Co., Inc. Address: 1199 Amboy Ave Scientific Programming Analyst City: Edison State: NJ ZIP: venkata_bhamidipati@merck.com middelasr@hotmail.com Phone:(267)