One way that you can manage query performance is to define limits for queries by specifying the following properties:

If LQE is performing intensive work, such as creating an index for a new data source or backing up the data, you might improve performance by temporarily disabling the query service.
When you enable query caching, query results are cached in the central database and are shared across all users who belong to the same access groups. Information about the groups that the query touches and the subset of those groups that the user belongs to is stored in the cache with the query results.

How it works: Two users, User 1 and User 2, are in the same resource group. User 1 runs Query A. If User 2 runs Query A within 120 seconds, he will get cached query results. If User 2 runs Query A after 120 seconds, the query runs again and he gets updated results. If you enable query load shedding, this behavior changes when the warning and critical thresholds are reached. See Query load shedding.
By defining query load shedding threshold values, you can control how Lifecycle Query Engine behaves when the query load is heavy and the thresholds are reached.
