Performance Analysis and Diagnosis for AWS Redshift in ConsumersHalt

Redshift Performance Reports

Question

ConsumersHalt (CH) is an Indian department collection chain.

There are 63 branches across 32 towns in India, with clothing, accessories, bags, shoes, jewelry, scents, faces, health and exquisiteness products, home furnishing and decor products. CH runs their existing operations and analytics infrastructure out of AWS which includes S3, EC2, Auto Scaling, CDN and also Redshift.

The Redshift platform is being used for advanced analytics, real time analytics and being actively used for past 2 years.

Suddenly performance issues are occurring in the application and administrator being a superuser needs to provide a list of reports in terms of current and historical performance of the cluster.

What types of tables/views can help access the performance related info for diagnosis. Select 3 options.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

Answer : A, D, F.

Option A is correct -STL system tables are generated from Amazon Redshift log files to provide a history of the system.

https://docs.aws.amazon.com/redshift/latest/dg/c_intro_STL_tables.html

Option B is incorrect -STL system tables are generated from Amazon Redshift log files to provide a history of the system.

https://docs.aws.amazon.com/redshift/latest/dg/c_intro_STL_tables.html

Option C is incorrect - STV tables are actually virtual system tables that contain snapshots of the current system data.

https://docs.aws.amazon.com/redshift/latest/dg/c_intro_STV_tables.html

Option D is correct - STV tables are actually virtual system tables that contain snapshots of the current system data.

https://docs.aws.amazon.com/redshift/latest/dg/c_intro_STV_tables.html

Option E is incorrect -System tables contain only subset of data.

https://docs.aws.amazon.com/redshift/latest/dg/c_intro_system_views.html

Option F is correct -The system catalogs store schema metadata, such as information about tables and columns.

System catalog tables have a PG prefix.

https://docs.aws.amazon.com/redshift/latest/dg/c_intro_catalog_views.html

In this scenario, the administrator needs to diagnose the performance issues in the Redshift cluster by analyzing current and historical performance-related data. The following tables/views can provide the required information:

A. STL system tables: These are system tables generated from Amazon Redshift log files and contain a history of system activity. They serve logging and can provide information on queries executed, query errors, system performance, and other system activity. Therefore, analyzing the STL tables can help identify performance issues and provide insights into system behavior.

B. STV system tables: These are virtual system tables that contain snapshots of the current system data. They serve snapshots and can provide information on system health and resource usage. Analyzing the STV tables can help identify resource contention issues, identify bottlenecks and provide insights into current system behavior.

C. System views: These views contain data found in several of the STL and STV system tables. They provide a convenient way to access performance-related information without the need to join multiple tables. Analyzing system views can provide a holistic view of system behavior and help identify performance issues.

D. The system catalogs: These store schema metadata such as information about tables and columns. Analyzing the system catalogs can help identify issues related to table design, such as data skew, distribution keys, and sort keys.

In summary, to diagnose performance issues in the Redshift cluster, the administrator can analyze the STL and STV system tables, system views, and system catalogs to identify resource contention, bottlenecks, query errors, and system behavior.