Skip to main content

Testing query performance in SAS

In our organization we had two SAS deployments, one is on premise and another is in AWS. We saw a slow performance of queries against the on premise database. We try to improve the performance by using several SAS options like READBUFF. But still we see there is a significant slower performance when compared to our on premise.

In one setup database is in on on-premise and SAS is in AWS, in another set up both SAS and Oracle database is in on premise. The issue reported is with the sas server in the AWS. We saw like for like query performing significantly slower than the on-premises server.

Below I am going to explain the process of testing which we took to find out the issue.

Testing method
I did my testing by running the query from Linux command line using the SQL plus utility. I created csv output using Oracle query and the sas query created the regular SAS dataset.

We run query against a table from our on premise database which had 5 million records and 200 plus column.

Full volume test
We used SAS to extract the full table and the READBUFF was set to be 100,000. The resulting data set was with the size of 9 gig and contains 5 million observation and 212 columns and observation length of 2000.

Results
We saw the queries from AWS environment are consistently slower than those from the on premise.
Increasing the buffer makes significant improvement in both the environment.

Oracle utility results
At worst case SAS AWS environment was 15 times slower than the on premise.
The worst result happened during that time were there are greater number of fetches.

SAS results
Tweaking the SAS options gave better performance than the default settings.
Even with similar settings AWS SAS services performed slow.


Script used:

On-Premises Server
Set Oracle Environment (setenv)

#!/bin/bash

export ORACLE_HOME=/app/oracle/product/11.2.0/client
export LD_LIBRARY_PATH=/app/oracle/product/11.2.0/client/lib:$LD_LIBRARY_PATH
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
export PATH=$PATH:$ORACLE_HOME/bin



Test Oracle Script (test1.sql)

SET COLSEP ,
SET HEADSEP OFF
SET TRIMSPOOL ON
SET PAGESIZE 0
SET NUMWIDTH 12
SET LINESIZE 50
SET TERMOUT OFF;

SPOOL /sas/saswork/test1.csv;
SELECT POST_TOWN, NUM_CARDS, BALANCE, GENDER
  FROM DAILY_APPLICATION; 

SPOOL OFF
SET TERMOUT ON;
QUIT;
/

AWS Server

Set Oracle Environment (setenv)

#!/bin/bash
export ORACLE_HOME=/app/oracle/product/11.2.0/client_1
export LD_LIBRARY_PATH=/app/oracle/product/11.2.0/client_1/lib:$LD_LIBRARY_PATH
export TNS_ADMIN=/tvssas/app/ora
export PATH=$ORACLE_HOME/bin:$PATH
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1


Test Oracle Script (test1.sql)
SET COLSEP ,
SET HEADSEP OFF
SET TRIMSPOOL ON
SET PAGESIZE 0
SET NUMWIDTH 12
SET LINESIZE 50
SET TERMOUT OFF;

SPOOL /saswork/ora/test1.csv;
SELECT POST_TOWN, NUM_CARDS, BALANCE, GENDER

  FROM DAILY_APPLICATION;
SPOOL OFF
SET TERMOUT ON;
QUIT;

/

Run Oracle Tests

Testing command line for SAS 9.2:
time sqlplus SAS_AMART/<<<password>>>@PMEGAMART.in.tvsmotor.com @test1.sql

Testing command line for SAS 9.4:
time sqlplus SAS_AMART/<<<password>>>@XMEGAMART.in.tvsmotor.com @test1.sql

The above will time the run, with the SQL statements in the file test1.sql.

Test SAS Script (test1.sas)
OPTIONS msglevel=i fullstimer;
OPTIONS sastrace=',,t,dsab' sastraceloc=saslog nostsuffix;

data timer;
   format tm1 time9.;
   tm1 = timepart( datetime() );
run;

 data test;
   set EDELWEISS.DAILY_APPLICATION( keep=POST_TOWN NUM_CARDS BALANCE GENDER
                                     readbuff=100000 );
run;

data _NULL_;
   set timer;
   format tm2 time9.;
   tm2 = timepart( datetime() );
   duration = tm2 - tm1;
   put duration=;
run;







Comments

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...

Insufficient authorization to access prgramname.lst

Issue: I had an issue with batch server. The code runs fine in SAS EG and SAS DI Studio but fails when I run with batchserver. Error seems to be ERROR: Insufficient authorization to access /opt/sasinside/Lev1/SASApp/Sas_Program.lst. NOTE: The SAS System stopped processing this step because of errors. Solution: When you execute on batch mode sas tries to save the output file (Sas_Program.lst) under /opt/sasinside/Lev1/SASApp where is no permission to write. We should add two system options to sasv9_usermods.cfg file to redirect this outputs to another directory. The options are following: -altprint <directory>  -print <directory> Where directory is a directory where you have access to write. You must provide this directory. The directory can be some shared location like: /share/sas/lst. If you decide to add this options these are the steps to follow: 1. Create or choose a driectory where your userid have write access. The userid is the ...