![]() ![]() We’ve already covered the basics of setting up Automatic WLM with Query Priorities from a very high-level, and in this post are going to give a first look at the performance we’re seeing with this new feature. Since writing that blog post, we ended up reverting all of our clusters to our well-tuned Manual WLM. For our use-case, this tradeoff didn’t work–the additional queueing caused unacceptable delays to our data pipeline. We first covered Redshift’s new Automatic WLM feature on our blog before Query Priority was fully released, and found mixed results: it was highly effective (maybe too effective!) at reducing the percentage of disk-based queries, but had the side effect of increasing overall queuing on our clusters since big queries consumed most of the memory for the cluster. This is a crucial performance enhancement that is needed to achieve Data SLAs. it allows you to prioritize some queries over other queries. This feature aims to address the main limitation of Auto WLM head-on, i.e. The AWS team recently released a new feature of their Automatic WLM that we’re really excited about: Query Priorities. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |