couple of days performance of the submitted queries are degrading even queries are not very complex and simple query which is executed on the small data is also performing badly. What is the solution you can
implement in this case?
1. You will be creating separate cluster for each department
2. You will be disabling the encryption of the data.
3. You will be disabling the cross-region snapshot replication.
4. You will be updating the configuration in Work Load Manager
5. You have to decrypt all the small table data in the cluster.
Correct Answer : 4 Exp : In the question it is saying that the recently queries started performing badly even simple query. This can be solved using Work Load Manager.
As the other options, like enabling and disabling encryption is not a correct choice. Hence, option-B and Option-E is out. Next option-A which is saying create a separate cluster for each department, not at all
logical thought. Your manager will certainly scold you, if you give this suggestion. Hence, option-A is out.
Also, you should not disable the cross-region snapshot. It does not help in improving the performance. Now see some concept about the Work Load Manager (WLM)
You can use workload management (WLM) to define multiple query queues and to route queries to the appropriate queues at runtime.
When you have multiple sessions or users running queries at the same time, some queries might consume cluster resources for long periods of time and affect the performance of other queries. For example, suppose one
group of users submits occasional complex, long-running queries that select and sort rows from several large tables. Another group frequently submits short queries that select only a few rows from one or two tables
and run in a few seconds. In this situation, the short-running queries might have to wait in a queue for a long-running query to complete.
You can improve system performance and your users experience by modifying your WLM configuration to create separate queues for the long-running queries and the short-running queries. At run time, you can route
queries to these queues according to user groups or query groups.
You can configure up to eight query queues and set the number of queries that can run in each of those queues concurrently. You can set up rules to route queries to particular queues based on the user running the
query or labels that you specify. You can also configure the amount of memory allocated to each queue, so that large queries run in queues with more memory than other queues. You can also configure the WLM timeout
property to limit long-running queries.
We recommend configuring your WLM query queues with a total of 15 or fewer query slots.
4
