Performance-centric cloud database virtual core sizing stack

A system including:

• database sizing circuitry configured to execute a database sizing stack, the database sizing circuitry configured to:
• at a data-staging layer of the database sizing stack:
• obtain historical data including data types, the data types including compute utilization type data, operation rate type data, and flush volume type data;
• and
• at a threading layer of the database sizing stack;
• based on the compute utilization type data, determine above-parameter utilization coincidences for multiple cores, the above-parameter utilization coincidences including instances of multiple ones of the multiple cores having simultaneous above-parameter utilization;
• when the above-parameter utilization coincidences exceed a threading threshold, determine that execution of a single-threaded task occurred despite simultaneous utilization of multiple cores;
• and
• when execution of a single-threaded task occurred is determined to have occurred, assert a single-threaded flag;
• when the single-threaded flag is asserted:
• skip a change-step diagnostic;
• and
• generate a provisional tier requisition token with a request for database-compute resources at a current database-compute tier;
• at a change layer of the database sizing stack:
• when the single-threaded flag is not asserted execute the change-step diagnostic by:
• accessing the compute utilization type data via a memory resource provided by a data-staging layer of the database sizing stack;
• and
• based on the compute utilization type data:
• determining whether compute utilization is below a down-step threshold;
• determining whether the compute utilization is below multi-step threshold;
• when compute utilization is below the down-step threshold, asserting a down-step flag;
• and
• when compute utilization is below the multi-step threshold, asserting a precision-step flag over the down-step flag, the multi-step threshold below the down-step threshold;
• at a step layer of the database sizing stack:
• when the down-step flag is asserted:
• access operation rate type data and flush volume type data via a memory resource provided by a data-staging layer of the database sizing stack;
• and
• based on the operation rate type data and flush volume type data:
• determine whether an operation rate is below the down-step threshold;
• determine whether log flush volume is below the down-step threshold;
• when both the operation rate and the log flush volume are below the down-step threshold, generate the provisional tier requisition token with a request for database-compute resources at a down-step database-compute tier;
• and
• when at least the operation rate or the log flush volume is above the down-step threshold, generate the provisional tier requisition token with a request for database-compute resources at the current database-compute tier;
• when the precision-step flag is asserted:
• access compute utilization type data, operation rate type data, and flush volume type data via a memory resource provided by a data-staging layer of the database sizing stack;
• and
• based on the compute utilization type data, operation rate type data, and flush volume type data:
• determine a compute-utilization-range and corresponding compute-step;
• determine an operation-rate-range and corresponding rate-step;
• determine a flush-volume-range and corresponding flush-step;
• determine a precision-step database-compute tier based on a smallest among the compute-step, the rate-step, and the flush-step;
• and
• generate the provisional tier requisition token with a request for database-compute resources at the precision-step database-compute tier;
• at a requisition layer of the database sizing stack after generating the provisional tier requisition token and based on a finalization directive, generate a finalized tier requisition token;
• and
• network interface circuitry configured to send the finalized tier requisition token to a host interface for control of database-compute resources.