Abstract: A method for intelligent query plan cache size management can be implemented. During execution of a plurality of incoming queries in a database management system, the method can measure actual compilation times of generating query execution plans for the plurality of incoming queries. The database management system can have a query execution plan cache which has a size that can store at least some of the query execution plans. The method can monitor differences between the actual compilation times and ideal compilation times of generating query execution plans for the plurality of incoming queries. The ideal compilation times can be estimated by assuming no query execution plan is evicted from the query execution plan cache. The method can adjust the size of the query execution plan cache based on the monitored differences.

Abstract: A computer-implemented method can measure query locality during execution of a plurality of incoming queries in a database management system. The database management system includes a query execution plan cache which has a size that can store at least some of query execution plans generated for the plurality of incoming queries. Based on the measured query locality, the method can adjust the size of the query execution plan cache.

Abstract: A method for intelligent query plan cache size management can be implemented. During execution of a plurality of incoming queries in a database management system, the method can measure actual compilation times of generating query execution plans for the plurality of incoming queries. The database management system can have a query execution plan cache which has a size that can store at least some of the query execution plans. The method can monitor differences between the actual compilation times and ideal compilation times of generating query execution plans for the plurality of incoming queries. The ideal compilation times can be estimated by assuming no query execution plan is evicted from the query execution plan cache. The method can adjust the size of the query execution plan cache based on the monitored differences.

Abstract: A computer-implemented method can measure query locality during execution of a plurality of incoming queries in a database management system. The database management system includes a query execution plan cache which has a size that can store at least some of query execution plans generated for the plurality of incoming queries. Based on the measured query locality, the method can adjust the size of the query execution plan cache.

Abstract: A system includes determination, for a first partitioned physical query operator in a query operator tree, of a partition-wise placement cost based on a cost of each table partition associated with the first partitioned physical query operator and a partition-wise placement cost of any child physical query operator of the first partitioned physical query operator, determination of a placement cost for the first partitioned physical query operator physical query operator for each of a plurality of operator execution locations based on the determined partition-wise placement cost, determination, for a logical query operator associated with the first partitioned physical query operator, of a merged placement cost for each of the plurality of operator execution locations, and determination an execution location for the first partitioned physical query operator based on the determined partition-wise placement cost.

Abstract: A system includes determination of a first partition-wise operation on a first database table partition of a first table located at a first server node and a first database table partition of a second table located at a second server node, determination of a first cost to execute the first partition-wise operation on the first server node, and a second cost to execute the first partition-wise operation on the second server node, determination of a second partition-wise operation on a result of the first partition-wise operation, determination of a third cost to execute the second partition-wise operation on the first server node based on the first cost and the second cost, and a fourth cost to execute the second partition-wise operation on the second server node based on the first cost and the second cost, determination of one of the first server node and the second server node to execute the second partition-wise operation based on the third cost and the fourth cost, and determination of one of the first ser

Abstract: A system includes determination of a first partition-wise operation on a first database table partition of a first table located at a first server node and a first database table partition of a second table located at a second server node, determination of a first cost to execute the first partition-wise operation on the first server node, and a second cost to execute the first partition-wise operation on the second server node, determination of a second partition-wise operation on a result of the first partition-wise operation, determination of a third cost to execute the second partition-wise operation on the first server node based on the first cost and the second cost, and a fourth cost to execute the second partition-wise operation on the second server node based on the first cost and the second cost, determination of one of the first server node and the second server node to execute the second partition-wise operation based on the third cost and the fourth cost, and determination of one of the first ser

Abstract: A system includes determination, for a first partitioned physical query operator in a query operator tree, of a partition-wise placement cost based on a cost of each table partition associated with the first partitioned physical query operator and a partition-wise placement cost of any child physical query operator of the first partitioned physical query operator, determination of a placement cost for the first partitioned physical query operator physical query operator for each of a plurality of operator execution locations based on the determined partition-wise placement cost, determination, for a logical query operator associated with the first partitioned physical query operator, of a merged placement cost for each of the plurality of operator execution locations, and determination an execution location for the first partitioned physical query operator based on the determined partition-wise placement cost.