Table of Contents | ||
---|---|---|
|
Note |
---|
Note that this feature is only enabled in certain domains by default. If you need to use it and is not enabled in your domain, contact the Devo support team. |
Not all queries are of equal importance, and often assigning a higher priority to heavy queries might be required in order to prioritize them. The query priority determines the amount of resources allocated to a query. These are the available query priority levels in Devo (listed from lowest to highest):
...
Rw ui steps macro | ||||||
---|---|---|---|---|---|---|
Go to Administration → Roles and select an existing role on the left tab (alternatively, you can create a New Role).
Add the Query priority permission to the role to enable the query priority selector in the navigation bar (if you are creating a new role, select also the other permissions and resources you want for this role).
Choose the Default query priority and Maximum query priority available for the role in the dropdown selectors that appear at the bottom. Note that the default value can only be set at Minimum or Normal. In the following capture, we are setting the default value for the role to Normal, and the maximum level they can select will be Urgent.
Click Apply Changes (or Create if you are creating a new role instead of modifying an existing one). The users with this role assigned will now be able to choose a different priority level for their session among the specified ones for their role (if you are creating a new role, don't forget to assign it to the desired users).
|
...
Note |
---|
Maximum and Urgent priority levels If a user changes the priority level to Maximum or Urgent, a warning is triggered advising that this could slow down other queries in the domain. Running queries with these priority levels has a great impact, so you should go back to Normal or Minimum priority as soon as possible. |