Mechanisms to predict system resource consumption of transactions
Techniques are disclosed pertaining to determining whether execution of a transaction will exceed a system resource threshold. A computer system stores a precomputed permissions data structure in association with particular data stored in a database. That precomputed data structure may be used to determine whether a user can access the particular data. The computer system may capture metric information that pertains to parameters involved in different types of transactions that can be performed to recompute the precomputed permissions data structure. Upon receiving a request to perform a transaction that involves recomputing the permissions data structure, the computer system, may determine, based on the metric information and the transaction's particular type, whether an execution of the transaction will exceed the system resource threshold. If the transaction exceeds the threshold, the computer system prevents the transaction from being executed and may provide suggestions to enable that transaction to be executed.
1. A method for determining whether a transaction that includes recomputing a precomputed permissions data structure will exceed a system resource threshold, the method comprising:
storing, by a computer system, the precomputed permissions data structure in association with particular data stored in a database, wherein the precomputed permissions data structure is usable to determine whether a user can access the particular data when processing a data request that is directed at the particular data;
capturing, by the computer system, metric information that pertains to a set of parameters involved in different types of transactions that can be performed to recompute the precomputed permissions data structure;
receiving, by the computer system, an update request whose processing involves executing the transaction, wherein the transaction is of a particular one of the different types of transactions that can be performed to recompute the precomputed permissions data structure; and
determining, by the computer system based on the metric information and the particular type of the transaction, whether an execution of the transaction will exceed the system resource threshold.
2. The method of claim 1 , wherein the precomputed permissions data structure is a table that includes access rules for a set of users and is linked to a separate table having the particular data.
3. The method of claim 1 , further comprising:
in response to determining that the execution of the transaction will exceed the system resource threshold, the computer system:
preventing the execution of the transaction; and
providing, to an issuer of the update request, a notification that the execution of the transaction has been prevented, wherein the notification identifies one or more solutions to enable the transaction to be executed.
4. The method of claim 1 , wherein the database stores data for a plurality of tenants of the computer system, and wherein the metric information specifies, for a given one of the plurality of tenants, tenant-specific values for the set of parameters.
5. The method of claim 1 , further comprising:
executing, by the computing system, one or more test transactions of the particular type of transaction; and
as a part of executing the one or more test transactions, the computer system capturing benchmark metric information pertaining to a resource consumption for the particular type of transaction, wherein a particular set of parameters involved in the particular type of transaction are derivable from the benchmark metric information.
6. The method of claim 1 , wherein the transaction includes a group membership change operation that involves modifying a number of users that is included in a particular group that is permitted to access at least a portion of the particular data.
7. The method of claim 6 , wherein the metric information identifies a number of records that are managed by users in the particular group.
8. The method of claim 1 , wherein the system resource threshold corresponds to an amount of memory that is permitted by the computer system to be used when executing a given transaction.
9. The method of claim 1 , further comprising:
storing, by the computer system, limit metadata describing value limits for ones of the set of parameters; and
preventing, by the computer system, the execution of the transaction in response to determining that a value of a parameter associated with the transaction exceeds a value limit identified by the limit metadata for that parameter.
10. A non-transitory computer readable medium having program instructions stored thereon that are executable by a computer system to cause the computer system to perform operations comprising:
storing a precomputed permissions data structure in association with particular data stored in a database, wherein the precomputed permissions data structure is usable to determine whether a user can access the particular data when processing a data request that is directed at the particular data;
capturing metric information that pertains to a set of parameters involved in different types of transactions that can be performed to recompute the precomputed permissions data structure;
receiving an update request whose processing involves executing a transaction, wherein the transaction is of a particular one of the different types of transactions that can be performed to recompute the precomputed permissions data structure; and
determining based on the metric information and the particular type of the transaction, whether an execution of the transaction will exceed a system resource threshold.
11. The non-transitory computer readable medium of claim 10 , wherein the operations further comprise:
in response to determining that the execution of the transaction will exceed the system resource threshold:
preventing the execution of the transaction; and
providing, to an issuer of the update request, a notification that the execution of the transaction has been prevented, wherein the notification identifies one or more solutions to enable the transaction to be executed.
12. The non-transitory computer readable medium of claim 10 , wherein the operations further comprise:
executing, one or more test transactions of the particular type of transaction; and
as a part of executing the one or more test transactions, capturing benchmark metric information pertaining to a resource consumption for the particular type of transaction, wherein a particular set of parameters involved in the particular type of transaction are derivable from the benchmark metric information.
13. The non-transitory computer readable medium of claim 10 , wherein the operations further comprise:
storing limit metadata describing value limits for ones of the set of parameters; and
preventing the execution of the transaction in response to determining that a value of a parameter associated with the transaction exceeds a value limit identified by the limit metadata for that parameter.
14. The non-transitory computer readable medium of claim 10 , wherein the metric information specifies, for a given one of a plurality of tenants that are hosted by the computer system, values for the set of parameters that are specific to the given tenant.
15. The non-transitory computer readable medium of claim 10 , wherein the system resource threshold corresponds to an amount of processing capability that is permitted by the computer system to be used when executing a given transaction.
16. A system, comprising:
at least one processor; and
memory having program instructions stored thereon that are executable by the at least one processor to cause the system to perform operations comprising:
storing a precomputed permissions data structure in association with particular data stored in a database, wherein the precomputed permissions data structure is usable to determine whether a user can access the particular data when processing a data request that is directed at the particular data;
capturing metric information that pertains to a set of parameters involved in different types of transactions that can be performed to recompute the precomputed permissions data structure;
receiving an update request whose processing involves executing a transaction, wherein the transaction is of a particular one of the different types of transactions that can be performed to recompute the precomputed permissions data structure; and
determining based on the metric information and the particular type of the transaction, whether an execution of the transaction will exceed a system resource threshold.
17. The system of claim 16 , wherein the operations further comprise:
in response to determining that the execution of the transaction will exceed the system resource threshold:
preventing the execution of the transaction; and
providing, to an issuer of the update request, a notification that the execution of the transaction has been prevented, wherein the notification identifies one or more solutions to enable the transaction to be executed.
18. The system of claim 16 , wherein the operations further comprise:
executing one or more test transactions of the particular type of transaction; and
as a part of executing the one or more test transactions, capturing benchmark metric information pertaining to a resource consumption for the particular type of transaction, wherein a particular set of parameters involved in the particular type of transaction are derivable from the benchmark metric information.
19. The system of claim 16 , wherein the operations further comprise:
storing limit metadata describing value limits for ones of the set of parameters; and
preventing the execution of the transaction in response to determining that a value of a parameter associated with the transaction exceeds a value limit identified by the limit metadata for that parameter.
20. The system of claim 16 , wherein the metric information specifies, for a given one of a plurality of tenants that are hosted by the system, values for the set of parameters that are specific to the given tenant.