A company uses an Amazon QuickSight dashboard to monitor usage of one of the company's applications. The company uses AWS Glue jobs to process data for the dashboard. The company stores the data in a single Amazon S3 bucket. The company adds new data every day. A data engineer discovers that dashboard queries are becoming slower over time. The data engineer determines that the root cause of the slowing queries is long-running AWS Glue jobs. Which actions should the data engineer take to improve the performance of the AWS Glue jobs? (Choose two.)
Select an option, then click Submit answer.
Reference / correct answer:
Partition the data that is in the S3 bucket. Organize the data by year, month, and day.
Most accepted answer: A. Partition the data that is in the S3 bucket. Organize the data by year, month, and day.
Community votes: A=1, B=1
Selected Answer: AB A. Partition the data that is in the S3 bucket. Organize the data by year, month, and day. • Partitioning data in Amazon S3 can significantly improve query performance. By organizing the data by year, month, and day, AWS Glue and Amazon QuickSight can scan only the relevant partitions of data, which reduces the amount of data read and processed. This approach is particularly effective for time-series data, where queries often target specific time ranges. B. Increase the AWS Glue instance size by scaling up the worker type. • Scaling up the worker type can provide more computational resources to the AWS Glue jobs, enabling them to process data faster. This can be especially beneficial when dealing with large datasets or complex transformations. It’s important to monitor the performance improvements and cost implications of scaling up. upvoted 11 times MLOPS_eng 1 year, 7 months ago How does partitioning data in S3 improve the performance of AWS Glue jobs? Partitioning data s3 improve the query performance, but the question was the action should the DE take to improve the performance of AWS Glue jobs ! upvoted 1 times ... Leo87656789 1 year, 9 months ago I would also go for A, B. But there are no worker types in AWS Glue. You can only increase the DPU. upvoted 1 times DevoteamAnalytix 1 year, 9 months ago Here you can find 5 different Worker types: https://docs.aws.amazon.com/glue/latest/dg/add-job.html upvoted 2 times ... tgv 1 year, 8 months ago It looks like there are various worker types in AWS Glue actually. I'll go with AB as well. "With AWS Glue, you only pay for the time your ETL job takes to run. There are no resources to manage, no upfront costs, and you are not charged for startup or shutdown time. You are charged an hourly rate based on the number of Data Processing Units (or DPUs) used to run your ETL job. A single Data Processing Unit (DPU) is also referred to as a worker. AWS Glue comes with three worker types to help you select the configuration that meets your job latency and cost requirements. Workers come in Standard, G.1X, G.2X, and G.025X configurations." https://docs.aws.amazon.com/glue/latest/dg/components-key-concepts.html upvoted 2 times ... ...
How does partitioning data in S3 improve the performance of AWS Glue jobs? Partitioning data s3 improve the query performance, but the question was the action should the DE take to improve the performance of AWS Glue jobs ! upvoted 1 times
I would also go for A, B. But there are no worker types in AWS Glue. You can only increase the DPU. upvoted 1 times DevoteamAnalytix 1 year, 9 months ago Here you can find 5 different Worker types: https://docs.aws.amazon.com/glue/latest/dg/add-job.html upvoted 2 times ... tgv 1 year, 8 months ago It looks like there are various worker types in AWS Glue actually. I'll go with AB as well. "With AWS Glue, you only pay for the time your ETL job takes to run. There are no resources to manage, no upfront costs, and you are not charged for startup or shutdown time. You are charged an hourly rate based on the number of Data Processing Units (or DPUs) used to run your ETL job. A single Data Processing Unit (DPU) is also referred to as a worker. AWS Glue comes with three worker types to help you select the configuration that meets your job latency and cost requirements. Workers come in Standard, G.1X, G.2X, and G.025X configurations." https://docs.aws.amazon.com/glue/latest/dg/components-key-concepts.html upvoted 2 times ...
Here you can find 5 different Worker types: https://docs.aws.amazon.com/glue/latest/dg/add-job.html upvoted 2 times
It looks like there are various worker types in AWS Glue actually. I'll go with AB as well. "With AWS Glue, you only pay for the time your ETL job takes to run. There are no resources to manage, no upfront costs, and you are not charged for startup or shutdown time. You are charged an hourly rate based on the number of Data Processing Units (or DPUs) used to run your ETL job. A single Data Processing Unit (DPU) is also referred to as a worker. AWS Glue comes with three worker types to help you select the configuration that meets your job latency and cost requirements. Workers come in Standard, G.1X, G.2X, and G.025X configurations." https://docs.aws.amazon.com/glue/latest/dg/components-key-concepts.html upvoted 2 times