OPTIMIZING EXECUTION OF OPERATIONS BY A DATABASE SYSTEM BASED ON ENERGY UTILIZATION AND/OR PERFORMANCE

[0001] None

[0002] Not Applicable.

[0003] Not Applicable.

[0004] This invention relates generally to computer networking and more particularly to database system and operation.

[0005] Computing devices are known to communicate data, process data, and/or store data. Such computing devices range from wireless smart phones, laptops, tablets, personal computers (PC), work stations, and video game devices, to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing device includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.

[0006] As is further known, a computer may effectively extend its CPU by using “cloud computing” to perform one or more computing functions (e.g., a service, an application, an algorithm, an arithmetic logic function, etc.) on behalf of the computer. Further, for large services, applications, and/or functions, cloud computing may be performed by multiple cloud computing resources in a distributed manner to improve the response time for completion of the service, application, and/or function.

[0007] Of the many applications a computer can perform, a database system is one of the largest and most complex applications. In general, a database system stores a large amount of data in a particular way for subsequent processing. In some situations, the hardware of the computer is a limiting factor regarding the speed at which a database system can process a particular function. In some other instances, the way in which the data is stored is a limiting factor regarding the speed of execution. In yet some other instances, restricted co-process options are a limiting factor regarding the speed of execution.

[0114] FIG. 1 is a schematic block diagram of an embodiment of a large-scale data processing network that includes data gathering devices (1, 1-1 through 1-n), data systems (2, 2-1 through 2-N), data storage systems (3, 3-1 through 3-n), a network 4, and a database system 10. The data gathering devices are computing devices that collect a wide variety of data and may further include sensors, monitors, measuring instruments, and/or other instrument for collecting data. The data gathering devices collect data in real-time (i.e., as it is happening) and provides it to data system 2-1 for storage and real-time processing of queries 5-1 to produce responses 6-1. As an example, the data gathering devices are computing in a factory collecting data regarding manufacturing of one or more products and the data system is evaluating queries to determine manufacturing efficiency, quality control, and/or product development status.

[0115] The data storage systems 3 store existing data. The existing data may originate from the data gathering devices or other sources, but the data is not real time data. For example, the data storage system stores financial data of a bank, a credit card company, or like financial institution. The data system 2-N processes queries 5-N regarding the data stored in the data storage systems to produce responses 6-N.

[0116] Data system 2 processes queries regarding real time data from data gathering devices and/or queries regarding non-real time data stored in the data storage system 3. The data system 2 produces responses in regard to the queries. Storage of real time and non-real time data, the processing of queries, and the generating of responses will be discussed with reference to one or more of the subsequent figures.

[0117] FIG. 1A is a schematic block diagram of an embodiment of a database system 10 that includes a parallelized data input sub-system 11, a parallelized data store, retrieve, and/or process sub-system 12, a parallelized query and response sub-system 13, system communication resources 14, an administrative sub-system 15, and a configuration sub-system 16. The system communication resources 14 include one or more of: wide area network (WAN) connections, local area network (LAN) connections, wireless connections, wireline connections, etc. to couple the sub-systems 11, 12, 13, 15, and 16 together.

[0118] Each of the sub-systems 11, 12, 13, 15, and 16 include a plurality of computing devices; an example of which is discussed with reference to one or more of FIGS. 7-9. Hereafter, the parallelized data input sub-system 11 may also be referred to as a data input sub-system, the parallelized data store, retrieve, and/or process sub-system may also be referred to as a data storage and processing sub-system, and the parallelized query and response sub-system 13 may also be referred to as a query and results sub-system.

[0119] In an example of operation, the parallelized data input sub-system 11 receives a data set (e.g., a table) that includes a plurality of records. A record includes a plurality of data fields. As a specific example, the data set includes tables of data from a data source. For example, a data source includes one or more computers. As another example, the data source is a plurality of machines. As yet another example, the data source is a plurality of data mining algorithms operating on one or more computers.

[0120] As is further discussed with reference to FIG. 15, the data source organizes its records of the data set into a table that includes rows and columns. The columns represent data fields of data for the rows. Each row corresponds to a record of data. For example, a table includes payroll information for a company's employees. Each row is an employee's payroll record. The columns include data fields for employee name, address, department, annual salary, tax deduction information, direct deposit information, etc.

[0121] The parallelized data input sub-system 11 processes a table to determine how to store it. For example, the parallelized data input sub-system 11 divides the data set into a plurality of data partitions. For each partition, the parallelized data input sub-system 11 divides it into a plurality of data segments based on a segmenting factor. The segmenting factor includes a variety of approaches of dividing a partition into segments. For example, the segment factor indicates a number of records to include in a segment. As another example, the segmenting factor indicates a number of segments to include in a segment group. As another example, the segmenting factor identifies how to segment a data partition based on storage capabilities of the data store and processing sub-system. As a further example, the segmenting factor indicates how many segments for a data partition based on a redundancy storage encoding scheme.

[0122] As an example of dividing a data partition into segments based on a redundancy storage encoding scheme, assume that it includes a 4 of 5 encoding scheme (meaning any 4 of 5 encoded data elements can be used to recover the data). Based on these parameters, the parallelized data input sub-system 11 divides a data partition into 5 segments: one corresponding to each of the data elements).

[0123] The parallelized data input sub-system 11 restructures the plurality of data segments to produce restructured data segments. For example, the parallelized data input sub-system 11 restructures records of a first data segment of the plurality of data segments based on a key field of the plurality of data fields to produce a first restructured data segment. The key field is common to the plurality of records. As a specific example, the parallelized data input sub-system 11 restructures a first data segment by dividing the first data segment into a plurality of data slabs (e.g., columns of a segment of a partition of a table). Using one or more of the columns as a key, or keys, the parallelized data input sub-system 11 sorts the data slabs. The restructuring to produce the data slabs is discussed in greater detail with reference to FIG. 4 and FIGS. 16-18.

[0124] The parallelized data input sub-system 11 also generates storage instructions regarding how sub-system 12 is to store the restructured data segments for efficient processing of subsequently received queries regarding the stored data. For example, the storage instructions include one or more of: a naming scheme, a request to store, a memory resource requirement, a processing resource requirement, an expected access frequency level, an expected storage duration, a required maximum access latency time, and other requirements associated with storage, processing, and retrieval of data.

[0125] A designated computing device of the parallelized data store, retrieve, and/or process sub-system 12 receives the restructured data segments and the storage instructions. The designated computing device (which is randomly selected, selected in a round robin manner, or by default) interprets the storage instructions to identify resources (e.g., itself, its components, other computing devices, and/or components thereof) within the computing device's storage cluster. The designated computing device then divides the restructured data segments of a segment group of a partition of a table into segment divisions based on the identified resources and/or the storage instructions. The designated computing device then sends the segment divisions to the identified resources for storage and subsequent processing in accordance with a query. The operation of the parallelized data store, retrieve, and/or process sub-system 12 is discussed in greater detail with reference to FIG. 6.

[0126] The parallelized query and response sub-system 13 receives queries regarding tables (e.g., data sets) and processes the queries prior to sending them to the parallelized data store, retrieve, and/or process sub-system 12 for execution. For example, the parallelized query and response sub-system 13 generates an initial query plan based on a data processing request (e.g., a query) regarding a data set (e.g., the tables). Sub-system 13 optimizes the initial query plan based on one or more of the storage instructions, the engaged resources, and optimization functions to produce an optimized query plan.

[0127] For example, the parallelized query and response sub-system 13 receives a specific query no. 1 regarding the data set no. 1 (e.g., a specific table). The query is in a standard query format such as Open Database Connectivity (ODBC), Java Database Connectivity (JDBC), and/or SPARK. The query is assigned to a node within the parallelized query and response sub-system 13 for processing. The assigned node identifies the relevant table, determines where and how it is stored, and determines available nodes within the parallelized data store, retrieve, and/or process sub-system 12 for processing the query.

[0128] In addition, the assigned node parses the query to create an abstract syntax tree. As a specific example, the assigned node converts an SQL (Structured Query Language) statement into a database instruction set. The assigned node then validates the abstract syntax tree. If not valid, the assigned node generates a SQL exception, determines an appropriate correction, and repeats. When the abstract syntax tree is validated, the assigned node then creates an annotated abstract syntax tree. The annotated abstract syntax tree includes the verified abstract syntax tree plus annotations regarding column names, data type(s), data aggregation or not, correlation or not, sub-query or not, and so on.

[0129] The assigned node then creates an initial query plan from the annotated abstract syntax tree. The assigned node optimizes the initial query plan using a cost analysis function (e.g., processing time, processing resources, etc.) and/or other optimization functions. Having produced the optimized query plan, the parallelized query and response sub-system 13 sends the optimized query plan to the parallelized data store, retrieve, and/or process sub-system 12 for execution. The operation of the parallelized query and response sub-system 13 is discussed in greater detail with reference to FIG. 5.

[0130] The parallelized data store, retrieve, and/or process sub-system 12 executes the optimized query plan to produce resultants and sends the resultants to the parallelized query and response sub-system 13. Within the parallelized data store, retrieve, and/or process sub-system 12, a computing device is designated as a primary device for the query plan (e.g., optimized query plan) and receives it. The primary device processes the query plan to identify nodes within the parallelized data store, retrieve, and/or process sub-system 12 for processing the query plan. The primary device then sends appropriate portions of the query plan to the identified nodes for execution. The primary device receives responses from the identified nodes and processes them in accordance with the query plan.

[0131] The primary device of the parallelized data store, retrieve, and/or process sub-system 12 provides the resulting response (e.g., resultants) to the assigned node of the parallelized query and response sub-system 13. For example, the assigned node determines whether further processing is needed on the resulting response (e.g., joining, filtering, etc.). If not, the assigned node outputs the resulting response as the response to the query (e.g., a response for query no. 1 regarding data set no. 1). If, however, further processing is determined, the assigned node further processes the resulting response to produce the response to the query. Having received the resultants, the parallelized query and response sub-system 13 creates a response from the resultants for the data processing request.

[0132] FIG. 2 is a schematic block diagram of an embodiment of the administrative sub-system 15 of FIG. 1A that includes one or more computing devices 18-1 through 18-n. Each of the computing devices executes an administrative processing function utilizing a corresponding administrative processing of administrative processing 19-1 through 19-n (which includes a plurality of administrative operations) that coordinates system level operations of the database system. Each computing device is coupled to an external network 17, or networks, and to the system communication resources 14 of FIG. 1A.

[0133] As will be described in greater detail with reference to one or more subsequent figures, a computing device includes a plurality of nodes and each node includes a plurality of processing core resources. Each processing core resource is capable of executing at least a portion of an administrative operation independently. This supports lock free and parallel execution of one or more administrative operations.

[0134] The administrative sub-system 15 functions to store metadata of the data set described with reference to FIG. 1A. For example, the storing includes generating the metadata to include one or more of an identifier of a stored table, the size of the stored table (e.g., bytes, number of columns, number of rows, etc.), labels for key fields of data segments, a data type indicator, the data owner, access permissions, available storage resources, storage resource specifications, software for operating the data processing, historical storage information, storage statistics, stored data access statistics (e.g., frequency, time of day, accessing entity identifiers, etc.) and any other information associated with optimizing operation of the database system 10.

[0135] FIG. 3 is a schematic block diagram of an embodiment of the configuration sub-system 16 of FIG. 1A that includes one or more computing devices 18-1 through 18-n. Each of the computing devices executes a configuration processing function 20-1 through 20-n (which includes a plurality of configuration operations) that coordinates system level configurations of the database system. Each computing device is coupled to the external network 17 of FIG. 2, or networks, and to the system communication resources 14 of FIG. 1A.

[0136] FIG. 4 is a schematic block diagram of an embodiment of the parallelized data input sub-system 11 of FIG. 1A that includes a bulk data sub-system 23 and a parallelized ingress sub-system 24. The bulk data sub-system 23 includes a plurality of computing devices 18-1 through 18-n. A computing device includes a bulk data processing function (e.g., 27-1) for receiving a table from a network storage system 21 (e.g., a server, a cloud storage service, etc.) and processing it for storage as generally discussed with reference to FIG. 1A.

[0137] The parallelized ingress sub-system 24 includes a plurality of ingress data sub-systems 25-1 through 25-p that each include a local communication resource of local communication resources 26-1 through 26-p and a plurality of computing devices 18-1 through 18-n. A computing device executes an ingress data processing function (e.g., 28-1) to receive streaming data regarding a table via a wide area network 22 and processing it for storage as generally discussed with reference to FIG. 1A. With a plurality of ingress data sub-systems 25-1 through 25-p, data from a plurality of tables can be streamed into the database system 10 at one time.

[0138] In general, the bulk data processing function is geared towards receiving data of a table in a bulk fashion (e.g., the table exists and is being retrieved as a whole, or portion thereof). The ingress data processing function is geared towards receiving streaming data from one or more data sources (e.g., receive data of a table as the data is being generated). For example, the ingress data processing function is geared towards receiving data from a plurality of machines in a factory in a periodic or continual manner as the machines create the data.

[0139] FIG. 5 is a schematic block diagram of an embodiment of a parallelized query and results sub-system 13 that includes a plurality of computing devices 18-1 through 18-n. Each of the computing devices executes a query (Q) & response (R) processing function 33-1 through 33-n. The computing devices are coupled to the wide area network 22 to receive queries (e.g., query no. 1 regarding data set no. 1) regarding tables and to provide responses to the queries (e.g., response for query no. 1 regarding the data set no. 1). For example, a computing device (e.g., 18-1) receives a query, creates an initial query plan therefrom, and optimizes it to produce an optimized plan. The computing device then sends components (e.g., one or more operations) of the optimized plan to the parallelized data store, retrieve, &/or process sub-system 12.

[0140] Processing resources of the parallelized data store, retrieve, &/or process sub-system 12 processes the components of the optimized plan to produce results components 32-1 through 32-n. The computing device of the Q&R sub-system 13 processes the result components to produce a query response.

[0141] The Q&R sub-system 13 allows for multiple queries regarding one or more tables to be processed concurrently. For example, a set of processing core resources of a computing device (e.g., one or more processing core resources) processes a first query and a second set of processing core resources of the computing device (or a different computing device) processes a second query.

[0142] As will be described in greater detail with reference to one or more subsequent figures, a computing device includes a plurality of nodes and each node includes multiple processing core resources such that a plurality of computing devices includes pluralities of multiple processing core resources A processing core resource of the pluralities of multiple processing core resources generates the optimized query plan and other processing core resources of the pluralities of multiple processing core resources generates other optimized query plans for other data processing requests. Each processing core resource is capable of executing at least a portion of the Q & R function. In an embodiment, a plurality of processing core resources of one or more nodes executes the Q & R function to produce a response to a query. The processing core resource is discussed in greater detail with reference to FIG. 13.

[0143] FIG. 6 is a schematic block diagram of an embodiment of a parallelized data store, retrieve, and/or process sub-system 12 that includes a plurality of computing devices, where each computing device includes a plurality of nodes and each node includes multiple processing core resources. Each processing core resource is capable of executing at least a portion of the function of the parallelized data store, retrieve, and/or process sub-system 12. The plurality of computing devices is arranged into a plurality of storage clusters. Each storage cluster includes a number of computing devices.

[0144] In an embodiment, the parallelized data store, retrieve, and/or process sub-system 12 includes a plurality of storage clusters 35-1 through 35-z. Each storage cluster includes a corresponding local communication resource 26-1 through 26-z and a number of computing devices 18-1 through 18-5. Each computing device executes an input, output, and processing (10 &P) processing function 34-1 through 34-5 to store and process data.

[0145] The number of computing devices in a storage cluster corresponds to the number of segments (e.g., a segment group) in which a data partitioned is divided. For example, if a data partition is divided into five segments, a storage cluster includes five computing devices. As another example, if the data is divided into eight segments, then there are eight computing devices in the storage clusters.

[0146] To store a segment group of segments 29 within a storage cluster, a designated computing device of the storage cluster interprets storage instructions to identify computing devices (and/or processing core resources thereof) for storing the segments to produce identified engaged resources. The designated computing device is selected by a random selection, a default selection, a round-robin selection, or any other mechanism for selection.

[0147] The designated computing device sends a segment to each computing device in the storage cluster, including itself. Each of the computing devices stores their segment of the segment group. As an example, five segments 29 of a segment group are stored by five computing devices of storage cluster 35-1. The first computing device 18-1-1 stores a first segment of the segment group; a second computing device 18-2-1 stores a second segment of the segment group; and so on. With the segments stored, the computing devices are able to process queries (e.g., query components from the Q&R sub-system 13) and produce appropriate result components.

[0148] While storage cluster 35-1 is storing and/or processing a segment group, the other storage clusters 35-2 through 35-n are storing and/or processing other segment groups. For example, a table is partitioned into three segment groups. Three storage clusters store and/or process the three segment groups independently. As another example, four tables are independently stored and/or processed by one or more storage clusters. As yet another example, storage cluster 35-1 is storing and/or processing a second segment group while it is storing/or and processing a first segment group.

[0149] FIG. 7 is a schematic block diagram of an embodiment of a computing device 18 that includes a plurality of nodes 37-1 through 37-4 coupled to a computing device controller hub 36. The computing device controller hub 36 includes one or more of a chipset, a quick path interconnect (QPI), and an ultra path interconnection (UPI). Each node 37-1 through 37-4 includes a central processing module 39-1 through 39-4, a main memory 40-1 through 40-4 (e.g., volatile memory), a disk memory 38-1 through 38-4 (non-volatile memory), and a network connection 41-1 through 41-4. In an alternate configuration, the nodes share a network connection, which is coupled to the computing device controller hub 36 or to one of the nodes as illustrated in subsequent figures.

[0150] In an embodiment, each node is capable of operating independently of the other nodes. This allows for large scale parallel operation of a query request, which significantly reduces processing time for such queries. In another embodiment, one or more node functions as co-processors to share processing requirements of a particular function, or functions.

[0151] FIG. 8 is a schematic block diagram of another embodiment of a computing device similar to the computing device of FIG. 7 with an exception that it includes a single network connection 41, which is coupled to the computing device controller hub 36. As such, each node coordinates with the computing device controller hub to transmit or receive data via the network connection.

[0152] FIG. 9 is a schematic block diagram of another embodiment of a computing device is similar to the computing device of FIG. 7 with an exception that it includes a single network connection 41, which is coupled to a central processing module of a node (e.g., to central processing module 39-1 of node 37-1). As such, each node coordinates with the central processing module via the computing device controller hub 36 to transmit or receive data via the network connection.

[0153] FIG. 10 is a schematic block diagram of an embodiment of a node 37 of computing device 18. The node 37 includes the central processing module 39, the main memory 40, the disk memory 38, and the network connection 41. The main memory 40 includes read only memory (RAM) and/or other form of volatile memory for storage of data and/or operational instructions of applications and/or of the operating system. The central processing module 39 includes a plurality of processing modules 44-1 through 44-n and an associated one or more cache memory 45. A processing module is as defined at the end of the detailed description.

[0154] The disk memory 38 includes a plurality of memory interface modules 43-1 through 43-n and a plurality of memory devices 42-1 through 42-n (e.g., non-volatile memory). The memory devices 42-1 through 42-n include, but are not limited to, solid state memory, disk drive memory, cloud storage memory, and other non-volatile memory. For each type of memory device, a different memory interface module 43-1 through 43-n is used. For example, solid state memory uses a standard, or serial, ATA (SATA), variation, or extension thereof, as its memory interface. As another example, disk drive memory devices use a small computer system interface (SCSI), variation, or extension thereof, as its memory interface.

[0155] In an embodiment, the disk memory 38 includes a plurality of solid state memory devices and corresponding memory interface modules. In another embodiment, the disk memory 38 includes a plurality of solid state memory devices, a plurality of disk memories, and corresponding memory interface modules.

[0156] The network connection 41 includes a plurality of network interface modules 46-1 through 46-n and a plurality of network cards 47-1 through 47-n. A network card includes a wireless LAN (WLAN) device (e.g., an IEEE 802.11n or another protocol), a LAN device (e.g., Ethernet), a cellular device (e.g., CDMA), etc. The corresponding network interface modules 46-1 through 46-n include a software driver for the corresponding network card and a physical connection that couples the network card to the central processing module 39 or other component(s) of the node.

[0157] The connections between the central processing module 39, the main memory 40, the disk memory 38, and the network connection 41 may be implemented in a variety of ways. For example, the connections are made through a node controller (e.g., a local version of the computing device controller hub 36). As another example, the connections are made through the computing device controller hub 36.

[0158] FIG. 11 is a schematic block diagram of an embodiment of a node 37 of a computing device 18 that is similar to the node of FIG. 10, with a difference in the network connection. In this embodiment, the node 37 includes a single network interface module 46 and a corresponding network card 47 configuration.

[0159] FIG. 12 is a schematic block diagram of an embodiment of a node 37 of a computing device 18 that is similar to the node of FIG. 10, with a difference in the network connection. In this embodiment, the node 37 connects to a network connection via the computing device controller hub 36.

[0160] FIG. 13 is a schematic block diagram of another embodiment of a node 37 of computing device 18 that includes processing core resources 48-1 through 48-n, a memory device (MD) bus 49, a processing module (PM) bus 50, a main memory 40 and a network connection 41. The network connection 41 includes the network card 47 and the network interface module 46 of FIG. 10. Each processing core resource 48 includes a corresponding processing module 44-1 through 44-n, a corresponding memory interface module 43-1 through 43-n, a corresponding memory device 42-1 through 42-n, and a corresponding cache memory 45-1 through 45-n. In this configuration, each processing core resource can operate independently of the other processing core resources. This further supports increased parallel operation of database functions to further reduce execution time.

[0161] The main memory 40 is divided into a computing device (CD) 56 section and a database (DB) 51 section. The database section includes a database operating system (OS) area 52, a disk area 53, a network area 54, and a general area 55. The computing device section includes a computing device operating system (OS) area 57 and a general area 58. Note that each section could include more or less allocated areas for various tasks being executed by the database system.

[0162] In general, the database OS 52 allocates main memory for database operations. Once allocated, the computing device OS 57 cannot access that portion of the main memory 40. This supports lock free and independent parallel execution of one or more operations.

[0163] FIG. 14 is a schematic block diagram of an embodiment of operating systems of a computing device 18. The computing device 18 includes a computer operating system 60 and a database overriding operating system (DB OS) 61. The computer OS 60 includes process management 62, file system management 63, device management 64, memory management 66, and security 65. The processing management 62 generally includes process scheduling 67 and inter-process communication and synchronization 68. In general, the computer OS 60 is a conventional operating system used by a variety of types of computing devices. For example, the computer operating system is a personal computer operating system, a server operating system, a tablet operating system, a cell phone operating system, etc.

[0164] The database overriding operating system (DB OS) 61 includes custom DB device management 69, custom DB process management 70 (e.g., process scheduling and/or inter-process communication & synchronization), custom DB file system management 71, custom DB memory management 72, and/or custom security 73. In general, the database overriding OS 61 provides hardware components of a node for more direct access to memory, more direct access to a network connection, improved independency, improved data storage, improved data retrieval, and/or improved data processing than the computing device OS.

[0165] In an example of operation, the database overriding OS 61 controls which operating system, or portions thereof, operate with each node and/or computing device controller hub of a computing device (e.g., via OS select 75-1 through 75-n when communicating with nodes 37-1 through 37-n and via OS select 75-m when communicating with the computing device controller hub 36). For example, device management of a node is supported by the computer operating system, while process management, memory management, and file system management are supported by the database overriding operating system. To override the computer OS, the database overriding OS provides instructions to the computer OS regarding which management tasks will be controlled by the database overriding OS. The database overriding OS also provides notification to the computer OS as to which sections of the main memory it is reserving exclusively for one or more database functions, operations, and/or tasks. One or more examples of the database overriding operating system are provided in subsequent figures.

[0166] The database system 10 can be implemented as a massive scale database system that is operable to process data at a massive scale. As used herein, a massive scale refers to a massive number of records of a single dataset and/or many datasets, such as millions, billions, and/or trillions of records that collectively include many Gigabytes, Terabytes, Petabytes, and/or Exabytes of data. As used herein, a massive scale database system refers to a database system operable to process data at a massive scale. The processing of data at this massive scale can be achieved via a large number, such as hundreds, thousands, and/or millions of computing devices 18, nodes 37, and/or processing core resources 48 performing various functionality of database system 10 described herein in parallel, for example, independently and/or without coordination.

[0167] Such processing of data at this massive scale cannot practically be performed by the human mind. In particular, the human mind is not equipped to perform processing of data at a massive scale. Furthermore, the human mind is not equipped to perform hundreds, thousands, and/or millions of independent processes in parallel, within overlapping time spans. The embodiments of database system 10 discussed herein improves the technology of database systems by enabling data to be processed at a massive scale efficiently and/or reliably.

[0168] In particular, the database system 10 can be operable to receive data and/or to store received data at a massive scale. For example, the parallelized input and/or storing of data by the database system 10 achieved by utilizing the parallelized data input sub-system 11 and/or the parallelized data store, retrieve, and/or process sub-system 12 can cause the database system 10 to receive records for storage at a massive scale, where millions, billions, and/or trillions of records that collectively include many Gigabytes, Terabytes, Petabytes, and/or Exabytes can be received for storage, for example, reliably, redundantly and/or with a guarantee that no received records are missing in storage and/or that no received records are duplicated in storage. This can include processing real-time and/or near-real time data streams from one or more data sources at a massive scale based on facilitating ingress of these data streams in parallel. To meet the data rates required by these one or more real-time data streams, the processing of incoming data streams can be distributed across hundreds, thousands, and/or millions of computing devices 18, nodes 37, and/or processing core resources 48 for separate, independent processing with minimal and/or no coordination. The processing of incoming data streams for storage at this scale and/or this data rate cannot practically be performed by the human mind. The processing of incoming data streams for storage at this scale and/or this data rate improves database system by enabling greater amounts of data to be stored in databases for analysis and/or by enabling real-time data to be stored and utilized for analysis. The resulting richness of data stored in the database system can improve the technology of database systems by improving the depth and/or insights of various data analyses performed upon this massive scale of data.

[0169] Additionally, the database system 10 can be operable to perform queries upon data at a massive scale. For example, the parallelized retrieval and processing of data by the database system 10 achieved by utilizing the parallelized query and results sub-system 13 and/or the parallelized data store, retrieve, and/or process sub-system 12 can cause the database system 10 to retrieve stored records at a massive scale and/or to and/or filter, aggregate, and/or perform query operators upon records at a massive scale in conjunction with query execution, where millions, billions, and/or trillions of records that collectively include many Gigabytes, Terabytes, Petabytes, and/or Exabytes can be accessed and processed in accordance with execution of one or more queries at a given time, for example, reliably, redundantly and/or with a guarantee that no records are inadvertently missing from representation in a query resultant and/or duplicated in a query resultant. To execute a query against a massive scale of records in a reasonable amount of time such as a small number of seconds, minutes, or hours, the processing of a given query can be distributed across hundreds, thousands, and/or millions of computing devices 18, nodes 37, and/or processing core resources 48 for separate, independent processing with minimal and/or no coordination. The processing of queries at this massive scale and/or this data rate cannot practically be performed by the human mind. The processing of queries at this massive scale improves the technology of database systems by facilitating greater depth and/or insights of query resultants for queries performed upon this massive scale of data.

[0170] Furthermore, the database system 10 can be operable to perform multiple queries concurrently upon data at a massive scale. For example, the parallelized retrieval and processing of data by the database system 10 achieved by utilizing the parallelized query and results sub-system 13 and/or the parallelized data store, retrieve, and/or process sub-system 12 can cause the database system 10 to perform multiple queries concurrently, for example, in parallel, against data at this massive scale, where hundreds and/or thousands of queries can be performed against the same, massive scale dataset within a same time frame and/or in overlapping time frames. To execute multiple concurrent queries against a massive scale of records in a reasonable amount of time such as a small number of seconds, minutes, or hours, the processing of a multiple queries can be distributed across hundreds, thousands, and/or millions of computing devices 18, nodes 37, and/or processing core resources 48 for separate, independent processing with minimal and/or no coordination. A given computing devices 18, nodes 37, and/or processing core resources 48 may be responsible for participating in execution of multiple queries at a same time and/or within a given time frame, where its execution of different queries occurs within overlapping time frames. The processing of many concurrent queries at this massive scale and/or this data rate cannot practically be performed by the human mind. The processing of concurrent queries improves the technology of database systems by facilitating greater numbers of users and/or greater numbers of analyses to be serviced within a given time frame and/or over time.

[0171] FIGS. 15-23 are schematic block diagrams of an example of processing a table or data set for storage in the database system 10. FIG. 15 illustrates an example of a data set or table that includes 32 columns and 80 rows, or records, that is received by the parallelized data input-subsystem. This is a very small table, but is sufficient for illustrating one or more concepts regarding one or more aspects of a database system. The table is representative of a variety of data ranging from insurance data, to financial data, to employee data, to medical data, and so on.

[0172] FIG. 16 illustrates an example of the parallelized data input-subsystem dividing the data set into two partitions. Each of the data partitions includes 40 rows, or records, of the data set. In another example, the parallelized data input-subsystem divides the data set into more than two partitions. In yet another example, the parallelized data input-subsystem divides the data set into many partitions and at least two of the partitions have a different number of rows.

[0173] FIG. 17 illustrates an example of the parallelized data input-subsystem dividing a data partition into a plurality of segments to form a segment group. The number of segments in a segment group is a function of the data redundancy encoding. In this example, the data redundancy encoding is single parity encoding from four data pieces; thus, five segments are created. In another example, the data redundancy encoding is a two parity encoding from four data pieces; thus, six segments are created. In yet another example, the data redundancy encoding is single parity encoding from seven data pieces; thus, eight segments are created.

[0174] FIG. 18 illustrates an example of data for segment 1 of the segments of FIG. 17. The segment is in a raw form since it has not yet been key column sorted. As shown, segment 1 includes 8 rows and 32 columns. The third column is selected as the key column and the other columns store various pieces of information for a given row (i.e., a record). The key column may be selected in a variety of ways. For example, the key column is selected based on a type of query (e.g., a query regarding a year, where a data column is selected as the key column). As another example, the key column is selected in accordance with a received input command that identified the key column. As yet another example, the key column is selected as a default key column (e.g., a date column, an ID column, etc.)

[0175] As an example, the table is regarding a fleet of vehicles. Each row represents data regarding a unique vehicle. The first column stores a vehicle ID, the second column stores make and model information of the vehicle. The third column stores data as to whether the vehicle is on or off. The remaining columns store data regarding the operation of the vehicle such as mileage, gas level, oil level, maintenance information, routes taken, etc.

[0176] With the third column selected as the key column, the other columns of the segment are to be sorted based on the key column. Prior to being sorted, the columns are separated to form data slabs. As such, one column is separated out to form one data slab.

[0177] FIG. 19 illustrates an example of the parallelized data input-subsystem dividing segment 1 of FIG. 18 into a plurality of data slabs. A data slab is a column of segment 1. In this figure, the data of the data slabs has not been sorted. Once the columns have been separated into data slabs, each data slab is sorted based on the key column. Note that more than one key column may be selected and used to sort the data slabs based on two or more other columns.

[0178] FIG. 20 illustrates an example of the parallelized data input-subsystem sorting the each of the data slabs based on the key column. In this example, the data slabs are sorted based on the third column which includes data of “on” or “off”. The rows of a data slab are rearranged based on the key column to produce a sorted data slab. Each segment of the segment group is divided into similar data slabs and sorted by the same key column to produce sorted data slabs.

[0179] FIG. 21 illustrates an example of each segment of the segment group sorted into sorted data slabs. The similarity of data from segment to segment is for the convenience of illustration. Note that each segment has its own data, which may or may not be similar to the data in the other sections.

[0180] FIG. 22 illustrates an example of a segment structure for a segment of the segment group. The segment structure for a segment includes the data & parity section, a manifest section, one or more index sections, and a statistics section. The segment structure represents a storage mapping of the data (e.g., data slabs and parity data) of a segment and associated data (e.g., metadata, statistics, key column(s), etc.) regarding the data of the segment. The sorted data slabs of FIG. 16 of the segment are stored in the data & parity section of the segment structure. The sorted data slabs are stored in the data & parity section in a compressed format or as raw data (i.e., non-compressed format). Note that a segment structure has a particular data size (e.g., 32 Giga-Bytes) and data is stored within coding block sizes (e.g., 4 Kilo-Bytes).

[0181] Before the sorted data slabs are stored in the data & parity section, or concurrently with storing in the data & parity section, the sorted data slabs of a segment are redundancy encoded. The redundancy encoding may be done in a variety of ways. For example, the redundancy encoding is in accordance with RAID 5, RAID 6, or RAID 10. As another example, the redundancy encoding is a form of forward error encoding (e.g., Reed Solomon, Trellis, etc.). As another example, the redundancy encoding utilizes an erasure coding scheme.

[0182] The manifest section stores metadata regarding the sorted data slabs. The metadata includes one or more of, but is not limited to, descriptive metadata, structural metadata, and/or administrative metadata. Descriptive metadata includes one or more of, but is not limited to, information regarding data such as name, an abstract, keywords, author, etc. Structural metadata includes one or more of, but is not limited to, structural features of the data such as page size, page ordering, formatting, compression information, redundancy encoding information, logical addressing information, physical addressing information, physical to logical addressing information, etc. Administrative metadata includes one or more of, but is not limited to, information that aids in managing data such as file type, access privileges, rights management, preservation of the data, etc.

[0183] The key column is stored in an index section. For example, a first key column is stored in index #0. If a second key column exists, it is stored in index #1. As such, for each key column, it is stored in its own index section. Alternatively, one or more key columns are stored in a single index section.

[0184] The statistics section stores statistical information regarding the segment and/or the segment group. The statistical information includes one or more of, but is not limited, to number of rows (e.g., data values) in one or more of the sorted data slabs, average length of one or more of the sorted data slabs, average row size (e.g., average size of a data value), etc. The statistical information includes information regarding raw data slabs, raw parity data, and/or compressed data slabs and parity data.

[0185] FIG. 23 illustrates the segment structures for each segment of a segment group having five segments. Each segment includes a data & parity section, a manifest section, one or more index sections, and a statistic section. Each segment is targeted for storage in a different computing device of a storage cluster. The number of segments in the segment group corresponds to the number of computing devices in a storage cluster. In this example, there are five computing devices in a storage cluster. Other examples include more or less than five computing devices in a storage cluster.

[0186] FIG. 24A illustrates an example of a query execution plan 2405 implemented by the database system 10 to execute one or more queries by utilizing a plurality of nodes 37. Each node 37 can be utilized to implement some or all of the plurality of nodes 37 of some or all computing devices 18-1-18-n, for example, of the of the parallelized data store, retrieve, and/or process sub-system 12, and/or of the parallelized query and results sub-system 13. The query execution plan can include a plurality of levels 2410. In this example, a plurality of H levels in a corresponding tree structure of the query execution plan 2405 are included. The plurality of levels can include a top, root level 2412; a bottom, IO level 2416, and one or more inner levels 2414. In some embodiments, there is exactly one inner level 2414, resulting in a tree of exactly three levels 2410.1, 2410.2, and 2410.3, where level 2410.H corresponds to level 2410.3. In such embodiments, level 2410.2 is the same as level 2410.H-1, and there are no other inner levels 2410.3-2410.H-2. Alternatively, any number of multiple inner levels 2414 can be implemented to result in a tree with more than three levels.

[0187] This illustration of query execution plan 2405 illustrates the flow of execution of a given query by utilizing a subset of nodes across some or all of the levels 2410. In this illustration, nodes 37 with a solid outline are nodes involved in executing a given query. Nodes 37 with a dashed outline are other possible nodes that are not involved in executing the given query, but could be involved in executing other queries in accordance with their level of the query execution plan in which they are included.

[0188] Each of the nodes of IO level 2416 can be operable to, for a given query, perform the necessary row reads for gathering corresponding rows of the query. These row reads can correspond to the segment retrieval to read some or all of the rows of retrieved segments determined to be required for the given query. Thus, the nodes 37 in level 2416 can include any nodes 37 operable to retrieve segments for query execution from its own storage or from storage by one or more other nodes; to recover segment for query execution via other segments in the same segment grouping by utilizing the redundancy error encoding scheme; and/or to determine which exact set of segments is assigned to the node for retrieval to ensure queries are executed correctly.

[0189] IO level 2416 can include all nodes in a given storage cluster 35 and/or can include some or all nodes in multiple storage clusters 35, such as all nodes in a subset of the storage clusters 35-1-35-z and/or all nodes in all storage clusters 35-1-35-z. For example, all nodes 37 and/or all currently available nodes 37 of the database system 10 can be included in level 2416. As another example, IO level 2416 can include a proper subset of nodes in the database system, such as some or all nodes that have access to stored segments and/or that are included in a segment set. In some cases, nodes 37 that do not store segments included in segment sets, that do not have access to stored segments, and/or that are not operable to perform row reads are not included at the IO level, but can be included at one or more inner levels 2414 and/or root level 2412.

[0190] The query executions discussed herein by nodes in accordance with executing queries at level 2416 can include retrieval of segments; extracting some or all necessary rows from the segments with some or all necessary columns; and sending these retrieved rows to a node at the next level 2410.H-1 as the query resultant generated by the node 37. For each node 37 at IO level 2416, the set of raw rows retrieved by the node 37 can be distinct from rows retrieved from all other nodes, for example, to ensure correct query execution. The total set of rows and/or corresponding columns retrieved by nodes 37 in the IO level for a given query can be dictated based on the domain of the given query, such as one or more tables indicated in one or more SELECT statements of the query, and/or can otherwise include all data blocks that are necessary to execute the given query.

[0191] Each inner level 2414 can include a subset of nodes 37 in the database system 10. Each level 2414 can include a distinct set of nodes 37 and/or some or more levels 2414 can include overlapping sets of nodes 37. The nodes 37 at inner levels are implemented, for each given query, to execute queries in conjunction with operators for the given query. For example, a query operator execution flow can be generated for a given incoming query, where an ordering of execution of its operators is determined (e.g. as an acyclic directed graph of operators), and this ordering is utilized to assign one or more operators of the query operator execution flow to each node in a given inner level 2414 for execution. For example, each node at a same inner level can be operable to execute a same set of operators for a given query, in response to being selected to execute the given query, upon incoming resultants generated by nodes at a directly lower level to generate its own resultants sent to a next higher level. In particular, each node at a same inner level can be operable to execute a same portion of a same query operator execution flow for a given query. In cases where there is exactly one inner level, each node selected to execute a query at a given inner level performs some or all of the given query's operators upon the raw rows received as resultants from the nodes at the IO level, such as the entire query operator execution flow and/or the portion of the query operator execution flow performed upon data that has already been read from storage by nodes at the IO level. In some cases, some operators beyond row reads are also performed by the nodes at the IO level. Each node at a given inner level 2414 can further perform a gather function to collect, union, and/or aggregate resultants sent from a previous level, for example, in accordance with one or more corresponding operators of the given query.

[0192] The root level 2412 can include exactly one node for a given query that gathers resultants from every node at the top-most inner level 2414. The node 37 at root level 2412 can perform additional query operators of the query and/or can otherwise collect, aggregate, and/or union the resultants from the top-most inner level 2414 to generate the final resultant of the query, which includes the resulting set of rows and/or one or more aggregated values, in accordance with the query, based on being performed on all rows required by the query. The root level node can be selected from a plurality of possible root level nodes, where different root nodes are selected for different queries. Alternatively, the same root node can be selected for all queries.

[0193] As depicted in FIG. 24A, resultants are sent by nodes upstream with respect to the tree structure of the query execution plan as they are generated, where the root node generates a final resultant of the query. While not depicted in FIG. 24A, nodes at a same level can share data and/or send resultants to each other, for example, in accordance with operators of the query at this same level dictating that data is sent between nodes.

[0194] In some cases, the IO level 2416 always includes the same set of nodes 37, such as a full set of nodes and/or all nodes that are in a storage cluster 35 that stores data required to process incoming queries. In some cases, the lowest inner level corresponding to level 2410.H-1 includes at least one node from the IO level 2416 in the possible set of nodes. In such cases, while each selected node in level 2410.H-1 is depicted to process resultants sent from other nodes 37 in FIG. 24A, each selected node in level 2410.H-1 that also operates as a node at the IO level further performs its own row reads in accordance with its query execution at the IO level, and gathers the row reads received as resultants from other nodes at the IO level with its own row reads for processing via operators of the query. One or more inner levels 2414 can also include nodes that are not included in IO level 2416, such as nodes 37 that do not have access to stored segments and/or that are otherwise not operable and/or selected to perform row reads for some or all queries.

[0195] The node 37 at root level 2412 can be fixed for all queries, where the set of possible nodes at root level 2412 includes only one node that executes all queries at the root level of the query execution plan. Alternatively, the root level 2412 can similarly include a set of possible nodes, where one node selected from this set of possible nodes for each query and where different nodes are selected from the set of possible nodes for different queries. In such cases, the nodes at inner level 2410.2 determine which of the set of possible root nodes to send their resultant to. In some cases, the single node or set of possible nodes at root level 2412 is a proper subset of the set of nodes at inner level 2410.2, and/or is a proper subset of the set of nodes at the IO level 2416. In cases where the root node is included at inner level 2410.2, the root node generates its own resultant in accordance with inner level 2410.2, for example, based on multiple resultants received from nodes at level 2410.3, and gathers its resultant that was generated in accordance with inner level 2410.2 with other resultants received from nodes at inner level 2410.2 to ultimately generate the final resultant in accordance with operating as the root level node.

[0196] In some cases where nodes are selected from a set of possible nodes at a given level for processing a given query, the selected node must have been selected for processing this query at each lower level of the query execution tree. For example, if a particular node is selected to process a node at a particular inner level, it must have processed the query to generate resultants at every lower inner level and the IO level. In such cases, each selected node at a particular level will always use its own resultant that was generated for processing at the previous, lower level, and will gather this resultant with other resultants received from other child nodes at the previous, lower level. Alternatively, nodes that have not yet processed a given query can be selected for processing at a particular level, where all resultants being gathered are therefore received from a set of child nodes that do not include the selected node.

[0197] The configuration of query execution plan 2405 for a given query can be determined in a downstream fashion, for example, where the tree is formed from the root downwards. Nodes at corresponding levels are determined from configuration information received from corresponding parent nodes and/or nodes at higher levels, and can each send configuration information to other nodes, such as their own child nodes, at lower levels until the lowest level is reached. This configuration information can include assignment of a particular subset of operators of the set of query operators that each level and/or each node will perform for the query. The execution of the query is performed upstream in accordance with the determined configuration, where IO reads are performed first, and resultants are forwarded upwards until the root node ultimately generates the query result.

[0198] Some or all features and/or functionality of FIG. 24A can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 24A based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to participate in a query execution plan of FIG. 24A as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24A can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 24A can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0199] FIG. 24B illustrates an embodiment of a node 37 executing a query in accordance with the query execution plan 2405 by implementing a query processing module 2435. The query processing module 2435 can be operable to execute a query operator execution flow 2433 determined by the node 37, where the query operator execution flow 2433 corresponds to the entirety of processing of the query upon incoming data assigned to the corresponding node 37 in accordance with its role in the query execution plan 2405. This embodiment of node 37 that utilizes a query processing module 2435 can be utilized to implement some or all of the plurality of nodes 37 of some or all computing devices 18-1-18-n, for example, of the of the parallelized data store, retrieve, and/or process sub-system 12, and/or of the parallelized query and results sub-system 13.

[0200] As used herein, execution of a particular query by a particular node 37 can correspond to the execution of the portion of the particular query assigned to the particular node in accordance with full execution of the query by the plurality of nodes involved in the query execution plan 2405. This portion of the particular query assigned to a particular node can correspond to execution plurality of operators indicated by a query operator execution flow 2433 (e.g. as an acyclic directed graph of operators). In particular, the execution of the query for a node 37 at an inner level 2414 and/or root level 2412 corresponds to generating a resultant by processing all incoming resultants received from nodes at a lower level of the query execution plan 2405 that send their own resultants to the node 37. The execution of the query for a node 37 at the IO level corresponds to generating all resultant data blocks by retrieving and/or recovering all segments assigned to the node 37.

[0201] Thus, as used herein, a node 37's full execution of a given query corresponds to only a portion of the query's execution across all nodes in the query execution plan 2405. In particular, a resultant generated by an inner level node 37's execution of a given query may correspond to only a portion of the entire query result, such as a subset of rows in a final result set, where other nodes generate their own resultants to generate other portions of the full resultant of the query. In such embodiments, a plurality of nodes at this inner level can fully execute queries on different portions of the query domain independently in parallel by utilizing the same query operator execution flow 2433. Resultants generated by each of the plurality of nodes at this inner level 2414 can be gathered into a final result of the query, for example, by the node 37 at root level 2412 if this inner level is the top-most inner level 2414 or the only inner level 2414. As another example, resultants generated by each of the plurality of nodes at this inner level 2414 can be further processed via additional operators of a query operator execution flow 2433 being implemented by another node at a consecutively higher inner level 2414 of the query execution plan 2405, where all nodes at this consecutively higher inner level 2414 all execute their own same query operator execution flow 2433.

[0202] As discussed in further detail herein, the resultant generated by a node 37 can include a plurality of resultant data blocks generated via a plurality of partial query executions. As used herein, a partial query execution performed by a node corresponds to generating a resultant based on only a subset of the query input received by the node 37. In particular, the query input corresponds to all resultants generated by one or more nodes at a lower level of the query execution plan that send their resultants to the node. However, this query input can correspond to a plurality of input data blocks received over time, for example, in conjunction with the one or more nodes at the lower level processing their own input data blocks received over time to generate their resultant data blocks sent to the node over time. Thus, the resultant generated by a node's full execution of a query can include a plurality of resultant data blocks, where each resultant data block is generated by processing a subset of all input data blocks as a partial query execution upon the subset of all data blocks via the query operator execution flow 2433.

[0203] As illustrated in FIG. 24B, the query processing module 2435 can be implemented by a single processing core resource 48 of the node 37. In such embodiments, each one of the processing core resources 48-1-48-n of a same node 37 can be executing at least one query concurrently via their own query processing module 2435, where a single node 37 implements each of set of operator processing modules 2435-1-2435-n via a corresponding one of the set of processing core resources 48-1-48-n. A plurality of queries can be concurrently executed by the node 37, where each of its processing core resources 48 can each independently execute at least one query within a same temporal period by utilizing a corresponding at least one query operator execution flow 2433 to generate at least one query resultant corresponding to the at least one query.

[0204] Some or all features and/or functionality of FIG. 24B can be performed via a corresponding node 37 in conjunction with system metadata applied across a plurality of nodes 37 that includes the given node, for example, where the given node 37 participates in some or all features and/or functionality of FIG. 24B based on receiving and storing the system metadata in local memory of given node 37 as configuration data and/or based on further accessing and/or executing this configuration data to process data blocks via a query processing module as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24B can optionally change and/or be updated over time, based on the system metadata applied across a plurality of nodes 37 that includes the given node being updated over time, and/or based on the given node updating its configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata.

[0205] FIG. 24C illustrates a particular example of a node 37 at the IO level 2416 of the query execution plan 2405 of FIG. 24A. A node 37 can utilize its own memory resources, such as some or all of its disk memory 38 and/or some or all of its main memory 40 to implement at least one memory drive 2425 that stores a plurality of segments 2424. Memory drives 2425 of a node 37 can be implemented, for example, by utilizing disk memory 38 and/or main memory 40. In particular, a plurality of distinct memory drives 2425 of a node 37 can be implemented via the plurality of memory devices 42-1-42-n of the node 37's disk memory 38.

[0206] Each segment 2424 stored in memory drive 2425 can be generated as discussed previously in conjunction with FIGS. 15-23. A plurality of records 2422 can be included in and/or extractable from the segment, for example, where the plurality of records 2422 of a segment 2424 correspond to a plurality of rows designated for the particular segment 2424 prior to applying the redundancy storage coding scheme as illustrated in FIG. 17. The records 2422 can be included in data of segment 2424, for example, in accordance with a column-format and/or other structured format. Each segment 2424 can further include parity data 2426 as discussed previously to enable other segments 2424 in the same segment group to be recovered via applying a decoding function associated with the redundancy storage coding scheme, such as a RAID scheme and/or erasure coding scheme, that was utilized to generate the set of segments of a segment group.

[0207] Thus, in addition to performing the first stage of query execution by being responsible for row reads, nodes 37 can be utilized for database storage, and can each locally store a set of segments in its own memory drives 2425. In some cases, a node 37 can be responsible for retrieval of only the records stored in its own one or more memory drives 2425 as one or more segments 2424. Executions of queries corresponding to retrieval of records stored by a particular node 37 can be assigned to that particular node 37. In other embodiments, a node 37 does not use its own resources to store segments. A node 37 can access its assigned records for retrieval via memory resources of another node 37 and/or via other access to memory drives 2425, for example, by utilizing system communication resources 14.

[0208] The query processing module 2435 of the node 37 can be utilized to read the assigned by first retrieving or otherwise accessing the corresponding redundancy-coded segments 2424 that include the assigned records its one or more memory drives 2425. Query processing module 2435 can include a record extraction module 2438 that is then utilized to extract or otherwise read some or all records from these segments 2424 accessed in memory drives 2425, for example, where record data of the segment is segregated from other information such as parity data included in the segment and/or where this data containing the records is converted into row-formatted records from the column-formatted row data stored by the segment. Once the necessary records of a query are read by the node 37, the node can further utilize query processing module 2435 to send the retrieved records all at once, or in a stream as they are retrieved from memory drives 2425, as data blocks to the next node 37 in the query execution plan 2405 via system communication resources 14 or other communication channels.

[0209] Some or all features and/or functionality of FIG. 24C can be performed via a corresponding node 37 in conjunction with system metadata applied across a plurality of nodes 37 that includes the given node, for example, where the given node 37 participates in some or all features and/or functionality of FIG. 24C based on receiving and storing the system metadata in local memory of given node 37 as configuration data and/or based on further accessing and/or executing this configuration data to read segments and/or extract rows from segments via a query processing module as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24C can optionally change and/or be updated over time, based on the system metadata applied across a plurality of nodes 37 that includes the given node being updated over time, and/or based on the given node updating its configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata.

[0210] FIG. 24D illustrates an embodiment of a node 37 that implements a segment recovery module 2439 to recover some or all segments that are assigned to the node for retrieval, in accordance with processing one or more queries, that are unavailable. Some or all features of the node 37 of FIG. 24D can be utilized to implement the node 37 of FIGS. 24B and 24C, and/or can be utilized to implement one or more nodes 37 of the query execution plan 2405 of FIG. 24A, such as nodes 37 at the IO level 2416. A node 37 may store segments on one of its own memory drives 2425 that becomes unavailable, or otherwise determines that a segment assigned to the node for execution of a query is unavailable for access via a memory drive the node 37 accesses via system communication resources 14. The segment recovery module 2439 can be implemented via at least one processing module of the node 37, such as resources of central processing module 39. The segment recovery module 2439 can retrieve the necessary number of segments 1-K in the same segment group as an unavailable segment from other nodes 37, such as a set of other nodes 37-1-37-K that store segments in the same storage cluster 35. Using system communication resources 14 or other communication channels, a set of external retrieval requests 1-K for this set of segments 1-K can be sent to the set of other nodes 37-1-37-K, and the set of segments can be received in response. This set of K segments can be processed, for example, where a decoding function is applied based on the redundancy storage coding scheme utilized to generate the set of segments in the segment group and/or parity data of this set of K segments is otherwise utilized to regenerate the unavailable segment. The necessary records can then be extracted from the unavailable segment, for example, via the record extraction module 2438, and can be sent as data blocks to another node 37 for processing in conjunction with other records extracted from available segments retrieved by the node 37 from its own memory drives 2425.

[0211] Note that the embodiments of node 37 discussed herein can be configured to execute multiple queries concurrently by communicating with nodes 37 in the same or different tree configuration of corresponding query execution plans and/or by performing query operations upon data blocks and/or read records for different queries. In particular, incoming data blocks can be received from other nodes for multiple different queries in any interleaving order, and a plurality of operator executions upon incoming data blocks for multiple different queries can be performed in any order, where output data blocks are generated and sent to the same or different next node for multiple different queries in any interleaving order. IO level nodes can access records for the same or different queries any interleaving order. Thus, at a given point in time, a node 37 can have already begun its execution of at least two queries, where the node 37 has also not yet completed its execution of the at least two queries.

[0212] A query execution plan 2405 can guarantee query correctness based on assignment data sent to or otherwise communicated to all nodes at the IO level ensuring that the set of required records in query domain data of a query, such as one or more tables required to be accessed by a query, are accessed exactly one time: if a particular record is accessed multiple times in the same query and/or is not accessed, the query resultant cannot be guaranteed to be correct. Assignment data indicating segment read and/or record read assignments to each of the set of nodes 37 at the IO level can be generated, for example, based on being mutually agreed upon by all nodes 37 at the IO level via a consensus protocol executed between all nodes at the IO level and/or distinct groups of nodes 37 such as individual storage clusters 35. The assignment data can be generated such that every record in the database system and/or in query domain of a particular query is assigned to be read by exactly one node 37. Note that the assignment data may indicate that a node 37 is assigned to read some segments directly from memory as illustrated in FIG. 24C and is assigned to recover some segments via retrieval of segments in the same segment group from other nodes 37 and via applying the decoding function of the redundancy storage coding scheme as illustrated in FIG. 24D.

[0213] Assuming all nodes 37 read all required records and send their required records to exactly one next node 37 as designated in the query execution plan 2405 for the given query, the use of exactly one instance of each record can be guaranteed. Assuming all inner level nodes 37 process all the required records received from the corresponding set of nodes 37 in the IO level 2416, via applying one or more query operators assigned to the node in accordance with their query operator execution flow 2433, correctness of their respective partial resultants can be guaranteed. This correctness can further require that nodes 37 at the same level intercommunicate by exchanging records in accordance with JOIN operations as necessary, as records received by other nodes may be required to achieve the appropriate result of a JOIN operation. Finally, assuming the root level node receives all correctly generated partial resultants as data blocks from its respective set of nodes at the penultimate, highest inner level 2414 as designated in the query execution plan 2405, and further assuming the root level node appropriately generates its own final resultant, the correctness of the final resultant can be guaranteed.

[0214] In some embodiments, each node 37 in the query execution plan can monitor whether it has received all necessary data blocks to fulfill its necessary role in completely generating its own resultant to be sent to the next node 37 in the query execution plan. A node 37 can determine receipt of a complete set of data blocks that was sent from a particular node 37 at an immediately lower level, for example, based on being numbered and/or have an indicated ordering in transmission from the particular node 37 at the immediately lower level, and/or based on a final data block of the set of data blocks being tagged in transmission from the particular node 37 at the immediately lower level to indicate it is a final data block being sent. A node 37 can determine the required set of lower level nodes from which it is to receive data blocks based on its knowledge of the query execution plan 2405 of the query. A node 37 can thus conclude when a complete set of data blocks has been received each designated lower level node in the designated set as indicated by the query execution plan 2405. This node 37 can therefore determine itself that all required data blocks have been processed into data blocks sent by this node 37 to the next node 37 and/or as a final resultant if this node 37 is the root node. This can be indicated via tagging of its own last data block, corresponding to the final portion of the resultant generated by the node, where it is guaranteed that all appropriate data was received and processed into the set of data blocks sent by this node 37 in accordance with applying its own query operator execution flow 2433.

[0215] In some embodiments, if any node 37 determines it did not receive all of its required data blocks, the node 37 itself cannot fulfill generation of its own set of required data blocks. For example, the node 37 will not transmit a final data block tagged as the “last” data block in the set of outputted data blocks to the next node 37, and the next node 37 will thus conclude there was an error and will not generate a full set of data blocks itself. The root node, and/or these intermediate nodes that never received all their data and/or never fulfilled their generation of all required data blocks, can independently determine the query was unsuccessful. In some cases, the root node, upon determining the query was unsuccessful, can initiate re-execution of the query by re-establishing the same or different query execution plan 2405 in a downward fashion as described previously, where the nodes 37 in this re-established query execution plan 2405 execute the query accordingly as though it were a new query. For example, in the case of a node failure that caused the previous query to fail, the new query execution plan 2405 can be generated to include only available nodes where the node that failed is not included in the new query execution plan 2405.

[0216] Some or all features and/or functionality of FIG. 24D can be performed via a corresponding node 37 in conjunction with system metadata applied across a plurality of nodes 37 that includes the given node, for example, where the given node 37 participates in some or all features and/or functionality of FIG. 24D based on receiving and storing the system metadata in local memory of given node 37 as configuration data and/or based on further accessing and/or executing this configuration data to recover segments via external retrieval requests and performing a rebuilding process upon corresponding segments as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24D can optionally change and/or be updated over time, based on the system metadata applied across a plurality of nodes 37 that includes the given node being updated over time, and/or based on the given node updating its configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata.

[0217] FIG. 24E illustrates an embodiment of an inner level 2414 that includes at least one shuffle node set 2485 of the plurality of nodes assigned to the corresponding inner level. A shuffle node set 2485 can include some or all of a plurality of nodes assigned to the corresponding inner level, where all nodes in the shuffle node set 2485 are assigned to the same inner level. In some cases, a shuffle node set 2485 can include nodes assigned to different levels 2410 of a query execution plan. A shuffle node set 2485 at a given time can include some nodes that are assigned to the given level, but are not participating in a query at that given time, as denoted with dashed outlines and as discussed in conjunction with FIG. 24A. For example, while a given one or more queries are being executed by nodes in the database system 10, a shuffle node set 2485 can be static, regardless of whether all of its members are participating in a given query at that time. In other cases, shuffle node set 2485 only includes nodes assigned to participate in a corresponding query, where different queries that are concurrently executing and/or executing in distinct time periods have different shuffle node sets 2485 based on which nodes are assigned to participate in the corresponding query execution plan. While FIG. 24E depicts multiple shuffle node sets 2485 of an inner level 2414, in some cases, an inner level can include exactly one shuffle node set, for example, that includes all possible nodes of the corresponding inner level 2414 and/or all participating nodes of the of the corresponding inner level 2414 in a given query execution plan.

[0218] While FIG. 24E depicts that different shuffle node sets 2485 can have overlapping nodes 37, in some cases, each shuffle node set 2485 includes a distinct set of nodes, for example, where the shuffle node sets 2485 are mutually exclusive. In some cases, the shuffle node sets 2485 are collectively exhaustive with respect to the corresponding inner level 2414, where all possible nodes of the inner level 2414, or all participating nodes of a given query execution plan at the inner level 2414, are included in at least one shuffle node set 2485 of the inner level 2414. If the query execution plan has multiple inner levels 2414, each inner level can include one or more shuffle node sets 2485. In some cases, a shuffle node set 2485 can include nodes from different inner levels 2414, or from exactly one inner level 2414. In some cases, the root level 2412 and/or the IO level 2416 have nodes included in shuffle node sets 2485. In some cases, the query execution plan 2405 includes and/or indicates assignment of nodes to corresponding shuffle node sets 2485 in addition to assigning nodes to levels 2410, where nodes 37 determine their participation in a given query as participating in one or more levels 2410 and/or as participating in one or more shuffle node sets 2485, for example, via downward propagation of this information from the root node to initiate the query execution plan 2405 as discussed previously.

[0219] The shuffle node sets 2485 can be utilized to enable transfer of information between nodes, for example, in accordance with performing particular operations in a given query that cannot be performed in isolation. For example, some queries require that nodes 37 receive data blocks from its children nodes in the query execution plan for processing, and that the nodes 37 additionally receive data blocks from other nodes at the same level 2410. In particular, query operations such as JOIN operations of a SQL query expression may necessitate that some or all additional records that were access in accordance with the query be processed in tandem to guarantee a correct resultant, where a node processing only the records retrieved from memory by its child IO nodes is not sufficient.

[0220] In some cases, a given node 37 participating in a given inner level 2414 of a query execution plan may send data blocks to some or all other nodes participating in the given inner level 2414, where these other nodes utilize these data blocks received from the given node to process the query via their query processing module 2435 by applying some or all operators of their query operator execution flow 2433 to the data blocks received from the given node. In some cases, a given node 37 participating in a given inner level 2414 of a query execution plan may receive data blocks to some or all other nodes participating in the given inner level 2414, where the given node utilizes these data blocks received from the other nodes to process the query via their query processing module 2435 by applying some or all operators of their query operator execution flow 2433 to the received data blocks.

[0221] This transfer of data blocks can be facilitated via a shuffle network 2480 of a corresponding shuffle node set 2485. Nodes in a shuffle node set 2485 can exchange data blocks in accordance with executing queries, for example, for execution of particular operators such as JOIN operators of their query operator execution flow 2433 by utilizing a corresponding shuffle network 2480. The shuffle network 2480 can correspond to any wired and/or wireless communication network that enables bidirectional communication between any nodes 37 communicating with the shuffle network 2480. In some cases, the nodes in a same shuffle node set 2485 are operable to communicate with some or all other nodes in the same shuffle node set 2485 via a direct communication link of shuffle network 2480, for example, where data blocks can be routed between some or all nodes in a shuffle network 2480 without necessitating any relay nodes 37 for routing the data blocks. In some cases, the nodes in a same shuffle set can broadcast data blocks.

[0222] In some cases, some nodes in a same shuffle node set 2485 do not have direct links via shuffle network 2480 and/or cannot send or receive broadcasts via shuffle network 2480 to some or all other nodes 37. For example, at least one pair of nodes in the same shuffle node set cannot communicate directly. In some cases, some pairs of nodes in a same shuffle node set can only communicate by routing their data via at least one relay node 37. For example, two nodes in a same shuffle node set do not have a direct communication link and/or cannot communicate via broadcasting their data blocks. However, if these two nodes in a same shuffle node set can each communicate with a same third node via corresponding direct communication links and/or via broadcast, this third node can serve as a relay node to facilitate communication between the two nodes. Nodes that are “further apart” in the shuffle network 2480 may require multiple relay nodes.

[0223] Thus, the shuffle network 2480 can facilitate communication between all nodes 37 in the corresponding shuffle node set 2485 by utilizing some or all nodes 37 in the corresponding shuffle node set 2485 as relay nodes, where the shuffle network 2480 is implemented by utilizing some or all nodes in the nodes shuffle node set 2485 and a corresponding set of direct communication links between pairs of nodes in the shuffle node set 2485 to facilitate data transfer between any pair of nodes in the shuffle node set 2485. Note that these relay nodes facilitating data blocks for execution of a given query within a shuffle node sets 2485 to implement shuffle network 2480 can be nodes participating in the query execution plan of the given query and/or can be nodes that are not participating in the query execution plan of the given query. In some cases, these relay nodes facilitating data blocks for execution of a given query within a shuffle node sets 2485 are strictly nodes participating in the query execution plan of the given query. In some cases, these relay nodes facilitating data blocks for execution of a given query within a shuffle node sets 2485 are strictly nodes that are not participating in the query execution plan of the given query.

[0224] Different shuffle node sets 2485 can have different shuffle networks 2480. These different shuffle networks 2480 can be isolated, where nodes only communicate with other nodes in the same shuffle node sets 2485 and/or where shuffle node sets 2485 are mutually exclusive. For example, data block exchange for facilitating query execution can be localized within a particular shuffle node set 2485, where nodes of a particular shuffle node set 2485 only send and receive data from other nodes in the same shuffle node set 2485, and where nodes in different shuffle node sets 2485 do not communicate directly and/or do not exchange data blocks at all. In some cases, where the inner level includes exactly one shuffle network, all nodes 37 in the inner level can and/or must exchange data blocks with all other nodes in the inner level via the shuffle node set via a single corresponding shuffle network 2480.

[0225] Alternatively, some or all of the different shuffle networks 2480 can be interconnected, where nodes can and/or must communicate with other nodes in different shuffle node sets 2485 via connectivity between their respective different shuffle networks 2480 to facilitate query execution. As a particular example, in cases where two shuffle node sets 2485 have at least one overlapping node 37, the interconnectivity can be facilitated by the at least one overlapping node 37, for example, where this overlapping node 37 serves as a relay node to relay communications from at least one first node in a first shuffle node sets 2485 to at least one second node in a second first shuffle node set 2485. In some cases, all nodes 37 in a shuffle node set 2485 can communicate with any other node in the same shuffle node set 2485 via a direct link enabled via shuffle network 2480 and/or by otherwise not necessitating any intermediate relay nodes. However, these nodes may still require one or more relay nodes, such as nodes included in multiple shuffle node sets 2485, to communicate with nodes in other shuffle node sets 2485, where communication is facilitated across multiple shuffle node sets 2485 via direct communication links between nodes within each shuffle node set 2485.

[0226] Note that these relay nodes facilitating data blocks for execution of a given query across multiple shuffle node sets 2485 can be nodes participating in the query execution plan of the given query and/or can be nodes that are not participating in the query execution plan of the given query. In some cases, these relay nodes facilitating data blocks for execution of a given query across multiple shuffle node sets 2485 are strictly nodes participating in the query execution plan of the given query. In some cases, these relay nodes facilitating data blocks for execution of a given query across multiple shuffle node sets 2485 are strictly nodes that are not participating in the query execution plan of the given query.

[0227] In some cases, a node 37 has direct communication links with its child node and/or parent node, where no relay nodes are required to facilitate sending data to parent and/or child nodes of the query execution plan 2405 of FIG. 24A. In other cases, at least one relay node may be required to facilitate communication across levels, such as between a parent node and child node as dictated by the query execution plan. Such relay nodes can be nodes within a and/or different same shuffle network as the parent node and child node, and can be nodes participating in the query execution plan of the given query and/or can be nodes that are not participating in the query execution plan of the given query.

[0228] Some or all features and/or functionality of FIG. 24E can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 24E based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to participate in one or more shuffle node sets of FIG. 24E as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24E can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 24E can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0229] FIG. 24F illustrates an embodiment of a database system that receives some or all query requests from one or more external requesting entities 2912. The external requesting entities 2912 can be implemented as a client device such as a personal computer and/or device, a server system, or other external system that generates and/or transmits query requests 2914. A query resultant 2920 can optionally be transmitted back to the same or different external requesting entity 2912. Some or all query requests processed by database system 10 as described herein can be received from external requesting entities 2912 and/or some or all query resultants generated via query executions described herein can be transmitted to external requesting entities 2912.

[0230] For example, a user types or otherwise indicates a query for execution via interaction with a computing device associated with and/or communicating with an external requesting entity. The computing device generates and transmits a corresponding query request 2914 for execution via the database system 10, where the corresponding query resultant 2920 is transmitted back to the computing device, for example, for storage by the computing device and/or for display to the corresponding user via a display device.

[0231] As another example, a query is automatically generated for execution via processing resources via a computing device and/or via communication with an external requesting entity implemented via at least one computing device. For example, the query is automatically generated and/or modified from a request generated via user input and/or received from a requesting entity in conjunction with implementing a query generator system, a query optimizer, generative artificial intelligence (AI), and/or other artificial intelligence and/or machine learning techniques. The computing device generates and transmits a corresponding query request 2914 for execution via the database system 10, where the corresponding query resultant 2920 is transmitted back to the computing device, for example, for storage by the computing device, transmission to another system, and/or for display to at least one corresponding user via a display device.

[0232] Some or all features and/or functionality of FIG. 24F can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 24F based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data, and/or based on further accessing and/or executing this configuration data to generate query execution plan data from query requests by implementing some or all of the operator flow generator module 2514 as part of its database functionality accordingly, and/or to participate in one or more query execution plans of a query execution module 2504 as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24F can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 24F can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0233] FIG. 24G illustrates an embodiment of a query processing system 2502 that generates a query operator execution flow 2517 from a query expression 2509 for execution via a query execution module 2504. The query processing system 2502 can be implemented utilizing, for example, the parallelized query and/or response sub-system 13 and/or the parallelized data store, retrieve, and/or process subsystem 12. The query processing system 2502 can be implemented by utilizing at least one computing device 18, for example, by utilizing at least one central processing module 39 of at least one node 37 utilized to implement the query processing system 2502. The query processing system 2502 can be implemented utilizing any processing module and/or memory of the database system 10, for example, communicating with the database system 10 via system communication resources 14.

[0234] As illustrated in FIG. 24G, an operator flow generator module 2514 of the query processing system 2502 can be utilized to generate a query operator execution flow 2517 for the query indicated in a query expression 2509. This can be generated based on a plurality of query operators indicated in the query expression and their respective sequential, parallelized, and/or nested ordering in the query expression (e.g. as an acyclic directed graph of operators), and/or based on optimizing the execution of the plurality of operators of the query expression. This query operator execution flow 2517 can include and/or be utilized to determine the query operator execution flow 2433 assigned to nodes 37 at one or more particular levels of the query execution plan 2405 and/or can include the operator execution flow to be implemented across a plurality of nodes 37, for example, based on a query expression indicated in the query request and/or based on optimizing the execution of the query expression.

[0235] In some cases, the operator flow generator module 2514 implements an optimizer to select the query operator execution flow 2517 based on determining the query operator execution flow 2517 is a most efficient and/or otherwise most optimal one of a set of query operator execution flow options and/or that arranges the operators in the query operator execution flow 2517 such that the query operator execution flow 2517 compares favorably to a predetermined efficiency threshold. For example, the operator flow generator module 2514 selects and/or arranges the plurality of operators of the query operator execution flow 2517 to implement the query expression in accordance with performing optimizer functionality, for example, by perform a deterministic function upon the query expression to select and/or arrange the plurality of operators in accordance with the optimizer functionality. This can be based on known and/or estimated processing times of different types of operators. This can be based on known and/or estimated levels of record filtering that will be applied by particular filtering parameters of the query. This can be based on selecting and/or deterministically utilizing a conjunctive normal form and/or a disjunctive normal form to build the query operator execution flow 2517 from the query expression. This can be based on selecting a determining a first possible serial ordering of a plurality of operators to implement the query expression based on determining the first possible serial ordering of the plurality of operators is known to be or expected to be more efficient than at least one second possible serial ordering of the same or different plurality of operators that implements the query expression. This can be based on ordering a first operator before a second operator in the query operator execution flow 2517 based on determining executing the first operator before the second operator results in more efficient execution than executing the second operator before the first operator. For example, the first operator is known to filter the set of records upon which the second operator would be performed to improve the efficiency of performing the second operator due to being executed upon a smaller set of records than if performed before the first operator. This can be based on other optimizer functionality that otherwise selects and/or arranges the plurality of operators of the query operator execution flow 2517 based on other known, estimated, and/or otherwise determined criteria.

[0236] A query execution module 2504 of the query processing system 2502 can execute the query expression via execution of the query operator execution flow 2517 to generate a query resultant. For example, the query execution module 2504 can be implemented via a plurality of nodes 37 that execute the query operator execution flow 2517. In particular, the plurality of nodes 37 of a query execution plan 2405 of FIG. 24A can collectively execute the query operator execution flow 2517. In such cases, nodes 37 of the query execution module 2504 can each execute their assigned portion of the query to produce data blocks as discussed previously, starting from IO level nodes propagating their data blocks upwards until the root level node processes incoming data blocks to generate the query resultant, where inner level nodes execute their respective query operator execution flow 2433 upon incoming data blocks to generate their output data blocks. The query execution module 2504 can be utilized to implement the parallelized query and results sub-system 13 and/or the parallelized data store, receive and/or process sub-system 12.

[0237] Some or all features and/or functionality of FIG. 24G can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 24G based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to generate query execution plan data from query requests by executing some or all operators of a query operator flow 2517 as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24G can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 24G can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0238] FIG. 24H presents an example embodiment of a query execution module 2504 that executes query operator execution flow 2517. Some or all features and/or functionality of the query execution module 2504 of FIG. 24H can implement the query execution module 2504 of FIG. 24G and/or any other embodiment of the query execution module 2504 discussed herein. Some or all features and/or functionality of the query execution module 2504 of FIG. 24H can optionally be utilized to implement the query processing module 2435 of node 37 in FIG. 24B and/or to implement some or all nodes 37 at inner levels 2414 of a query execution plan 2405 of FIG. 24A.

[0239] The query execution module 2504 can execute the determined query operator execution flow 2517 by performing a plurality of operator executions of operators 2520 of the query operator execution flow 2517 in a corresponding plurality of sequential operator execution steps. Each operator execution step of the plurality of sequential operator execution steps can correspond to execution of a particular operator 2520 of a plurality of operators 2520-1-2520-M of a query operator execution flow 2433.

[0240] In some embodiments, a single node 37 executes the query operator execution flow 2517 as illustrated in FIG. 24H as their operator execution flow 2433 of FIG. 24B, where some or all nodes 37 such as some or all inner level nodes 37 utilize the query processing module 2435 as discussed in conjunction with FIG. 24B to generate output data blocks to be sent to other nodes 37 and/or to generate the final resultant by applying the query operator execution flow 2517 to input data blocks received from other nodes and/or retrieved from memory as read and/or recovered records. In such cases, the entire query operator execution flow 2517 determined for the query as a whole can be segregated into multiple query operator execution sub-flows 2433 that are each assigned to the nodes of each of a corresponding set of inner levels 2414 of the query execution plan 2405, where all nodes at the same level execute the same query operator execution flows 2433 upon different received input data blocks. In some cases, the query operator execution flows 2433 applied by each node 37 includes the entire query operator execution flow 2517, for example, when the query execution plan includes exactly one inner level 2414. In other embodiments, the query processing module 2435 is otherwise implemented by at least one processing module the query execution module 2504 to execute a corresponding query, for example, to perform the entire query operator execution flow 2517 of the query as a whole.

[0241] A single operator execution by the query execution module 2504, such as via a particular node 37 executing its own query operator execution flows 2433, by executing one of the plurality of operators of the query operator execution flow 2433. As used herein, an operator execution corresponds to executing one operator 2520 of the query operator execution flow 2433 on one or more pending data blocks 2537 in an operator input data set 2522 of the operator 2520. The operator input data set 2522 of a particular operator 2520 includes data blocks that were outputted by execution of one or more other operators 2520 that are immediately below the particular operator in a serial ordering of the plurality of operators of the query operator execution flow 2433. In particular, the pending data blocks 2537 in the operator input data set 2522 were outputted by the one or more other operators 2520 that are immediately below the particular operator via one or more corresponding operator executions of one or more previous operator execution steps in the plurality of sequential operator execution steps. Pending data blocks 2537 of an operator input data set 2522 can be ordered, for example as an ordered queue, based on an ordering in which the pending data blocks 2537 are received by the operator input data set 2522. Alternatively, an operator input data set 2522 is implemented as an unordered set of pending data blocks 2537.

[0242] If the particular operator 2520 is executed for a given one of the plurality of sequential operator execution steps, some or all of the pending data blocks 2537 in this particular operator 2520's operator input data set 2522 are processed by the particular operator 2520 via execution of the operator to generate one or more output data blocks. For example, the input data blocks can indicate a plurality of rows, and the operation can be a SELECT operator indicating a simple predicate. The output data blocks can include only proper subset of the plurality of rows that meet the condition specified by the simple predicate.

[0243] Once a particular operator 2520 has performed an execution upon a given data block 2537 to generate one or more output data blocks, this data block is removed from the operator's operator input data set 2522. In some cases, an operator selected for execution is automatically executed upon all pending data blocks 2537 in its operator input data set 2522 for the corresponding operator execution step. In this case, an operator input data set 2522 of a particular operator 2520 is therefore empty immediately after the particular operator 2520 is executed. The data blocks outputted by the executed data block are appended to an operator input data set 2522 of an immediately next operator 2520 in the serial ordering of the plurality of operators of the query operator execution flow 2433, where this immediately next operator 2520 will be executed upon its data blocks once selected for execution in a subsequent one of the plurality of sequential operator execution steps.

[0244] Operator 2520.1 can correspond to a bottom-most operator 2520 in the serial ordering of the plurality of operators 2520.1-2520.M. As depicted in FIG. 24G, operator 2520.1 has an operator input data set 2522.1 that is populated by data blocks received from another node as discussed in conjunction with FIG. 24B, such as a node at the IO level of the query execution plan 2405. Alternatively these input data blocks can be read by the same node 37 from storage, such as one or more memory devices that store segments that include the rows required for execution of the query. In some cases, the input data blocks are received as a stream over time, where the operator input data set 2522.1 may only include a proper subset of the full set of input data blocks required for execution of the query at a particular time due to not all of the input data blocks having been read and/or received, and/or due to some data blocks having already been processed via execution of operator 2520.1. In other cases, these input data blocks are read and/or retrieved by performing a read operator or other retrieval operation indicated by operator 2520.

[0245] Note that in the plurality of sequential operator execution steps utilized to execute a particular query, some or all operators will be executed multiple times, in multiple corresponding ones of the plurality of sequential operator execution steps. In particular, each of the multiple times a particular operator 2520 is executed, this operator is executed on set of pending data blocks 2537 that are currently in their operator input data set 2522, where different ones of the multiple executions correspond to execution of the particular operator upon different sets of data blocks that are currently in their operator queue at corresponding different times.

[0246] As a result of this mechanism of processing data blocks via operator executions performed over time, at a given time during the query's execution by the node 37, at least one of the plurality of operators 2520 has an operator input data set 2522 that includes at least one data block 2537. At this given time, one more other ones of the plurality of operators 2520 can have input data sets 2522 that are empty. For example, a given operator's operator input data set 2522 can be empty as a result of one or more immediately prior operators 2520 in the serial ordering not having been executed yet, and/or as a result of the one or more immediately prior operators 2520 not having been executed since a most recent execution of the given operator.

[0247] Some types of operators 2520, such as JOIN operators or aggregating operators such as SUM, AVERAGE, MAXIMUM, or MINIMUM operators, require knowledge of the full set of rows that will be received as output from previous operators to correctly generate their output. As used herein, such operators 2520 that must be performed on a particular number of data blocks, such as all data blocks that will be outputted by one or more immediately prior operators in the serial ordering of operators in the query operator execution flow 2517 to execute the query, are denoted as “blocking operators.” Blocking operators are only executed in one of the plurality of sequential execution steps if their corresponding operator queue includes all of the required data blocks to be executed. For example, some or all blocking operators can be executed only if all prior operators in the serial ordering of the plurality of operators in the query operator execution flow 2433 have had all of their necessary executions completed for execution of the query, where none of these prior operators will be further executed in accordance with executing the query.

[0248] Some operator output generated via execution of an operator 2520, alternatively or in addition to being added to the input data set 2522 of a next sequential operator in the sequential ordering of the plurality of operators of the query operator execution flow 2433, can be sent to one or more other nodes 37 in a same shuffle node set as input data blocks to be added to the input data set 2522 of one or more of their respective operators 2520. In particular, the output generated via a node's execution of an operator 2520 that is serially before the last operator 2520.M of the node's query operator execution flow 2433 can be sent to one or more other nodes 37 in a same shuffle node set as input data blocks to be added to the input data set 2522 of a respective operators 2520 that is serially after the last operator 2520.1 of the query operator execution flow 2433 of the one or more other nodes 37.

[0249] As a particular example, the node 37 and the one or more other nodes 37 in a shuffle node set all execute queries in accordance with the same, common query operator execution flow 2433, for example, based on being assigned to a same inner level 2414 of the query execution plan 2405. The output generated via a node's execution of a particular operator 2520.i this common query operator execution flow 2433 can be sent to the one or more other nodes 37 in a same shuffle node set as input data blocks to be added to the input data set 2522 the next operator 2520.i+1, with respect to the serialized ordering of the query of this common query operator execution flow 2433 of the one or more other nodes 37. For example, the output generated via a node's execution of a particular operator 2520.i is added input data set 2522 the next operator 2520.i+1 of the same node's query operator execution flow 2433 based on being serially next in the sequential ordering and/or is alternatively or additionally added to the input data set 2522 of the next operator 2520.i+1 of the common query operator execution flow 2433 of the one or more other nodes in a same shuffle node set based on being serially next in the sequential ordering.

[0250] In some cases, in addition to a particular node sending this output generated via a node's execution of a particular operator 2520.i to one or more other nodes to be input data set 2522 the next operator 2520.i+1 in the common query operator execution flow 2433 of the one or more other nodes 37, the particular node also receives output generated via some or all of these one or more other nodes' execution of this particular operator 2520.i in their own query operator execution flow 2433 upon their own corresponding input data set 2522 for this particular operator. The particular node adds this received output of execution of operator 2520.i by the one or more other nodes to the be input data set 2522 of its own next operator 2520.i+1.

[0251] This mechanism of sharing data can be utilized to implement operators that require knowledge of all records of a particular table and/or of a particular set of records that may go beyond the input records retrieved by children or other descendants of the corresponding node. For example, JOIN operators can be implemented in this fashion, where the operator 2520.i+1 corresponds to and/or is utilized to implement JOIN operator and/or a custom-join operator of the query operator execution flow 2517, and where the operator 2520.i+1 thus utilizes input received from many different nodes in the shuffle node set in accordance with their performing of all of the operators serially before operator 2520.i+1 to generate the input to operator 2520.i+1.

[0252] Some or all features and/or functionality of FIG. 24H can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 24H based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data execute some or all operators of a query operator flow 2517 as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24H can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 24H can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0253] FIG. 24I illustrates an example embodiment of multiple nodes 37 that execute a query operator execution flow 2433. For example, these nodes 37 are at a same level 2410 of a query execution plan 2405, and receive and perform an identical query operator execution flow 2433 in conjunction with decentralized execution of a corresponding query. Each node 37 can determine this query operator execution flow 2433 based on receiving the query execution plan data for the corresponding query that indicates the query operator execution flow 2433 to be performed by these nodes 37 in accordance with their participation at a corresponding inner level 2414 of the corresponding query execution plan 2405 as discussed in conjunction with FIG. 24G. This query operator execution flow 2433 utilized by the multiple nodes can be the full query operator execution flow 2517 generated by the operator flow generator module 2514 of FIG. 24G. This query operator execution flow 2433 can alternatively include a sequential proper subset of operators from the query operator execution flow 2517 generated by the operator flow generator module 2514 of FIG. 24G, where one or more other sequential proper subsets of the query operator execution flow 2517 are performed by nodes at different levels of the query execution plan.

[0254] Each node 37 can utilize a corresponding query processing module 2435 to perform a plurality of operator executions for operators of the query operator execution flow 2433 as discussed in conjunction with FIG. 24H. This can include performing an operator execution upon input data sets 2522 of a corresponding operator 2520, where the output of the operator execution is added to an input data set 2522 of a sequentially next operator 2520 in the operator execution flow, as discussed in conjunction with FIG. 24H, where the operators 2520 of the query operator execution flow 2433 are implemented as operators 2520 of FIG. 24H. Some or operators 2520 can correspond to blocking operators that must have all required input data blocks generated via one or more previous operators before execution. Each query processing module can receive, store in local memory, and/or otherwise access and/or determine necessary operator instruction data for operators 2520 indicating how to execute the corresponding operators 2520.

[0255] Some or all features and/or functionality of FIG. 24I can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 24I based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to execute some or all operators of a query operator flow 2517 in parallel with other nodes, send data blocks to a parent node, and/or process data blocks from child nodes as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 24I can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 24I can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0256] FIG. 24J illustrates an embodiment of a query execution module 2504 that executes each of a plurality of operators of a given operator execution flow 2517 via a corresponding one of a plurality of operator execution modules 3215. The operator execution modules 3215 of FIG. 24J can be implemented to execute any operators 2520 being executed by a query execution module 2504 for a given query as described herein.

[0257] In some embodiments, a given node 37 can optionally execute one or more operators, for example, when participating in a corresponding query execution plan 2405 for a given query, by implementing some or all features and/or functionality of the operator execution module 3215, for example, by implementing its operator processing module 2435 to execute one or more operator execution modules 3215 for one or more operators 2520 being processed by the given node 37. For example, a plurality of nodes of a query execution plan 2405 for a given query execute their operators based on implementing corresponding query processing modules 2435 accordingly.

[0258] FIG. 24K illustrates an embodiment of database storage 2450 operable to store a plurality of database tables 2712, such as relational database tables or other database tables as described previously herein. Database storage 2450 can be implemented via the parallelized data store, retrieve, and/or process sub-system 12, via memory drives 2425 of one or more nodes 37 implementing the database storage 2450, and/or via other memory and/or storage resources of database system 10. The database tables 2712 can be stored as segments as discussed in conjunction with FIGS. 15-23 and/or FIGS. 24B-24D. A database table 2712 can be implemented as one or more datasets and/or a portion of a given dataset, such as the dataset of FIG. 15.

[0259] A given database table 2712 can be stored based on being received for storage, for example, via the parallelized ingress sub-system 24 and/or via other data ingress. Alternatively or in addition, a given database table 2712 can be generated and/or modified by the database system 10 itself based on being generated as output of a query executed by query execution module 2504, such as a Create Table As Select (CTAS) query or Insert query.

[0260] A given database table 2712 can be in accordance with a schema 2409 defining columns of the database table, where records 2422 correspond to rows having values 2708 for some or all of these columns. Different database tables can have different numbers of columns and/or different datatypes for values stored in different columns. For example, the set of columns 2707.1_A-2707.C_A of schema 2709.A for database table 2712.A can have a different number of columns than and/or can have different datatypes for some or all columns of the set of columns 2707.1_B-2707.C_B of schema 2709.B for database table 2712.B. The schema 2409 for a given n database table 2712 can denote same or different datatypes for some or all of its set of columns. For example, some columns are variable-length and other columns are fixed-length. As another example, some columns are integers, other columns are binary values, other columns are Strings, and/or other columns are char types.

[0261] Row reads performed during query execution, such as row reads performed at the IO level of a query execution plan 2405, can be performed by reading values 2708 for one or more specified columns 2707 of the given query for some or all rows of one or more specified database tables, as denoted by the query expression defining the query to be performed. Filtering, join operations, and/or values included in the query resultant can be further dictated by operations to be performed upon the read values 2708 of these one or more specified columns 2707.

[0262] FIG. 24L illustrates an embodiment of a dataset 2502 having one or more columns 3023 implemented as array fields 2712. Some or all features and/or functionality of the dataset 2502 of FIG. 24L can be utilized to implement one or more of the database tables 2712 of FIG. 24K and/or any embodiment of any database table and/or dataset received, stored, and processed via the database system 10 as described herein.

[0263] Columns 3023 implemented as array fields 2712 can include array structures 2718 as values 3024 for some or all rows. A given array structure 2718 can have a set of elements 2709.1-2709.M. The value of M can be fixed for a given array field 2712, or can be different for different array structures 2718 of a given array field 2712. In embodiments where the number of elements is fixed, different array fields 2712 can have different fixed numbers of array elements 2709, for example, where a first array field 2712.A has array structures having M elements, and where a second array field 2712.B has array structures having N elements.

[0264] Note that a given array structure 2718 of a given array field can optionally have zero elements, where such array structures are considered as empty arrays satisfying the empty array condition. An empty array structure 2718 is distinct from a null value 3852, as it is a defined structure as an array 2718, despite not being populated with any values. For example, consider an example where an array field for rows corresponding to people is implemented to note a list of spouse names for all marriages of each person. An empty array for this array field for a first given row denotes a first corresponding person was never married, while a null value for this array field for a second given row denotes that it is unknown as to whether the second corresponding person was ever married, or who they were married to.

[0265] Array elements 2709 of a given array structure can have the same or different data type. In some embodiments, data types of array elements 2709 can be fixed for a given array field (e.g. all array elements 2709 of all array structures 2718 of array field 2712.A are string values, and all array elements 2709 of all array structures 2718 of array field 2712.B are integer values). In other embodiments, data types of array elements 2709 can be different for a given array field and/or a given array structure.

[0266] Some array structures 2718 that are non-empty can have one or more array elements having the null value 3852, where the corresponding value 3024 thus meets the null-inclusive array condition. This is distinct from the null value condition 3842, as the value 3024 itself is not null, but is instead an array structure 2718 having some or all of its array elements 2709 with values of null. Continuing example where an array field for rows corresponding to people is implemented to note a list of spouse names for all marriages of each person, a null value for this array field for the second given row denotes that it is unknown as to whether the second corresponding person was ever married or who they were married to, while a null value within an array structure for a third given row denotes that the name of the spouse for a corresponding one of a set of marriages of the person is unknown.

[0267] Some array structures 2718 that are non-empty can have all non-null values for its array elements 2709, where all corresponding array elements 2709 were populated and/or defined. Some array structures 2718 that are non-empty can have values for some of its array elements 2709 that are null, and values for others of its array elements 2709 that are non-null values.

[0268] Some array structures 2718 that are non-empty can have values for all of its array elements 2709 that are null. This is still distinct from the case where the value 3024 denotes a value of null with no array structure 2718. Continuing example where an array field for rows corresponding to people is implemented to note a list of spouse names for all marriages of each person, a null value for this array field for the second given row denotes that it is unknown as to whether the second corresponding person was ever married, how many times they were married or who they were married to, while the array structure for the third given row denotes a set of three null values and non-null values, denoting that the person was married three times, but the names of the spouses for all three marriages are unknown.

[0269] FIGS. 24M-24N illustrates an example embodiment of a query execution module 2504 of a database system 10 that executes queries via generation, storage, and/or communication of a plurality of column data streams 2968 corresponding to a plurality of columns. Some or all features and/or functionality of query execution module 2504 of FIGS. 24M-24N can implement any embodiment of query execution module 2504 described herein and/or any performance of query execution described herein. Some or all features and/or functionality of column data streams 2968 of FIGS. 24M-24N can implement any embodiment of data blocks 2537 and/or other communication of data between operators 2520 of a query operator execution flow 2517 when executed by a query execution module 2504, for example, via a corresponding plurality of operator execution modules 3215.

[0270] As illustrated in FIG. 24M, in some embodiments, data values of each given column 2915 are included in data blocks of their own respective column data stream 2968. Each column data stream 2968 can correspond to one given column 2915, where each given column 2915 is included in one data stream included in and/or referenced by output data blocks generated via execution of one or more operator execution module 3215, for example, to be utilized as input by one or more other operator execution modules 3215. Different columns can be designated for inclusion in different data streams. For example, different column streams are written do different portions of memory, such as different sets of memory fragments of query execution memory resources.

[0271] As illustrated in FIG. 24N, each data block 2537 of a given column data stream 2968 can include values 2918 for the respective column for one or more corresponding rows 2916. In the example of FIG. 24N, each data block includes values for V corresponding rows, where different data blocks in the column data stream include different respective sets of V rows, for example, that are each a subset of a total set of rows to be processed. In other embodiments, different data blocks can have different numbers of rows. The subsets of rows across a plurality of data blocks 2537 of a given column data stream 2968 can be mutually exclusive and collectively exhaustive with respect to the full output set of rows, for example, emitted by a corresponding operator execution module 3215 as output.

[0272] Values 2918 of a given row utilized in query execution are thus dispersed across different A given column 2915 can be implemented as a column 2707 having corresponding values 2918 implemented as values 2708 read from database table 2712 read from database storage 2450, for example, via execution of corresponding IO operators. Alternatively or in addition, a given column 2915 can be implemented as a column 2707 having new and/or modified values generated during query execution, for example, via execution of an extend expression and/or other operation. Alternatively or in addition, a given column 2915 can be implemented as a new column generated during query execution having new values generated accordingly, for example, via execution of an extend expression and/or other operation. The set of column data streams 2968 generated and/or emitted between operators in query execution can correspond to some or all columns of one or more tables 2712 and/or new columns of an existing table and/or of a new table generated during query execution.

[0273] Additional column streams emitted by the given operator execution module can have their respective values for the same full set of output rows across for other respective columns. For example, the values across all column streams are in accordance with a consistent ordering, where a first row's values 2918.1.1-2918.1.C for columns 2915.1-2915.C are included first in every respective column data stream, where a second row's values 2918.2.1-2918.2.C for columns 2915.1-2915.C are included second in every respective column data stream, and so on. In other embodiments, rows are optionally ordered differently in different column streams. Rows can be identified across column streams based on consistent ordering of values, based on being mapped to and/or indicating row identifiers, or other means.

[0274] As a particular example, for every fixed-length column, a huge block can be allocated to initialize a fixed length column stream, which can be implemented via mutable memory as a mutable memory column stream, and/or for every variable-length column, another huge block can be allocated to initialize a binary stream, which can be implemented via mutable memory as a mutable memory binary stream. A given column data stream 2968 can be continuously appended with fixed length values to data runs of contiguous memory and/or may grow the underlying huge page memory region to acquire more contiguous runs and/or fragments of memory.

[0275] In other embodiments, rather than emitting data blocks with values 2918 for different columns in different column streams, values 2918 for a set of multiple columns can be emitted in a same multi-column data stream.

[0276] FIG. 24O illustrates an example of operator execution modules 3215.C that each write their output memory blocks to one or more memory fragments 2622 of query execution memory resources 3045 and/or that each read/process input data blocks based on accessing the one or more memory fragments 2622 Some or all features and/or functionality of the operator execution modules 3215 of FIG. 24O can implement the operator execution modules of FIG. 24J and/or can implement any query execution described herein. The data blocks 2537 can implement the data blocks of column streams of FIGS. 24M and/or 24N, and/or any operator 2520's input data blocks and/or output data blocks described herein.

[0277] A given operator execution module 3215.A for an operator that is a child operator of the operator executed by operator execution module 3215.B can emit its output data blocks for processing by operator execution module 3215.B based on writing each of a stream of data blocks 2537.1-2537.K of data stream 2917.A to contiguous or non-contiguous memory fragments 2622 at one or more corresponding memory locations 2951 of query execution memory resources 3045.

[0278] Operator execution module 3215.A can generate these data blocks 2537.1-2537.K of data stream 2917.A in conjunction with execution of the respective operator on incoming data. This incoming data can correspond to one or more other streams of data blocks 2537 of another data stream 2917 accessed in memory resources 3045 based on being written by one or more child operator execution modules corresponding to child operators of the operator executed by operator execution module 3215.A. Alternatively or in addition, the incoming data is read from database storage 2450 and/or is read from one or more segments stored on memory drives, for example, based on the operator executed by operator execution module 3215.A being implemented as an IO operator.

[0279] The parent operator execution module 3215.B of operator execution module 3215.A can generate its own output data blocks 2537.1-2537.J of data stream 2917.B based on execution of the respective operator upon data blocks 2537.1-2537.K of data stream 2917.A. Executing the operator can include reading the values from and/or performing operations toy filter, aggregate, manipulate, generate new column values from, and/or otherwise determine values that are written to data blocks 2537.1-2537.J.

[0280] In other embodiments, the operator execution module 3215.B does not read the values from these data blocks, and instead forwards these data blocks, for example, where data blocks 2537.1-2537.J include memory reference data for the data blocks 2537.1-2537.K to enable one or more parent operator modules, such as operator execution module 3215.C, to access and read the values from forwarded streams.

[0281] In the case where operator execution module 3215.A has multiple parents, the data blocks 2537.1-2537.K of data stream 2917.A can be read, forwarded, and/or otherwise processed by each parent operator execution module 3215 independently in a same or similar fashion. Alternatively or in addition, in the case where operator execution module 3215.B has multiple children, each child's emitted set of data blocks 2537 of a respective data stream 2917 can be read, forwarded, and/or otherwise processed by operator execution module 3215.B in a same or similar fashion.

[0282] The parent operator execution module 3215.C of operator execution module 3215.B can similarly read, forward, and/or otherwise process data blocks 2537.1-2537.J of data stream 2917.B based on execution of the respective operator to render generation and emitting of its own data blocks in a similar fashion. Executing the operator can include reading the values from and/or performing operations to filter, aggregate, manipulate, generate new column values from, and/or otherwise process data blocks 2537.1-2537.J to determine values that are written to its own output data. For example, the operator execution module 3215.C reads data blocks 2537.1-2537.K of data stream 2917.A and/or the operator execution module 3215.B writes data blocks 2537.1-2537.J of data stream 2917.B. As another example, the operator execution module 3215.C reads data blocks 2537.1-2537.K of data stream 2917.A, or data blocks of another descendent, based on having been forwarded, where corresponding memory reference information denoting the location of these data blocks is read and processed from the received data blocks data blocks 2537.1-2537.J of data stream 2917.B enable accessing the values from data blocks 2537.1-2537.K of data stream 2917.A. As another example, the operator execution module 3215.B does not read the values from these data blocks, and instead forwards these data blocks, for example, where data blocks 2537.1-2537.J include memory reference data for the data blocks 2537.1-2537.J to enable one or more parent operator modules to read these forwarded streams.

[0283] This pattern of reading and/or processing input data blocks from one or more children for use in generating output data blocks for one or more parents can continue until ultimately a final operator, such as an operator executed by a root level node, generates a query resultant, which can itself be stored as data blocks in this fashion in query execution memory resources and/or can be transmitted to a requesting entity for display and/or storage.

[0284] For example, rather than accessing this large data for some or all potential records prior to filtering in a query execution, for example, via IO level 2416 of a corresponding query execution plan 2405 as illustrated in FIGS. 24A and 24C, and/or rather than passing this large data to other nodes 37 for processing, for example, from IO level nodes 37 to inner level nodes 37 and/or between any nodes 37 as illustrated in FIGS. 24A, 24B, and 24C, this large data is not accessed until a final stage of a query. As a particular example, this large data of the projected field is simply joined at the end of the query for the corresponding outputted rows that meet query predicates of the query. This ensures that, rather than accessing and/or passing the large data of these fields for some or all possible records that may be projected in the resultant, only the large data of these fields for final, filtered set of records that meet the query predicates are accessed and projected.

[0285] FIG. 24P illustrates an embodiment of a database system 10 that implements a segment generator 2507 to generate segments 2424. Some or all features and/or functionality of the database system 10 of FIG. 24P can implement any embodiment of the database system 10 described herein. Some or all features and/or functionality of segments 2424 of FIG. 24P can implement any embodiment of segment 2424 described herein.

[0286] A plurality of records 2422.1-2422.Z of one or more datasets 2505 to be converted into segments can be processed to generate a corresponding plurality of segments 2424.1-2424.Y. Each segment can include a plurality of column slabs 2610.1-2610.C corresponding to some or all of the C columns of the set of records.

[0287] In some embodiments, the dataset 2505 can correspond to a given database table 2712. In some embodiments, the dataset 2505 can correspond to only portion of a given database table 2712 (e.g. the most recently received set of records of a stream of records received for the table over time), where other datasets 2505 are later processed to generate new segments as more records are received over time. In some embodiments, the dataset 2505 can correspond to multiple database tables. The dataset 2505 optionally includes non-relational records and/or any records/files/data that is received from/generated by a given data source multiple different data sources.

[0288] Each record 2422 of the incoming dataset 2505 can be assigned to be included in exactly one segment 2424. In this example, segment 2424.1 includes at least records 2422.3 and 2422.7, while segment 2424 includes at least records 2422.1 and 2422.9. All of the Z records can be guaranteed to be included in exactly one segment by segment generator 2507. Rows are optionally grouped into segments based on a cluster-key based grouping or other grouping by same or similar column values of one or more columns. Alternatively, rows are optionally grouped randomly, in accordance with a round robin fashion, or by any other means.

[0289] A given row 2422 can thus have all of its column values 2708.1-2708.C included in exactly one given segment 2424, where these column values are dispersed across different column slabs 2610 based on which columns each column value corresponds. This division of column values into different column slabs can implement the columnar-format of segments described herein. The generation of column slabs can optionally include further processing of each set of column values assigned to each column slab. For example, some or all column slabs are optionally compressed and stored as compressed column slabs.

[0290] The database storage 2450 can thus store one or more datasets as segments 2424, for example, where these segments 2424 are accessed during query execution to identify/read values of rows of interest as specified in query predicates, where these identified rows/the respective values are further filtered/processed/etc., for example, via operators 2520 of a corresponding query operator execution flow 2517, or otherwise accordance with the query to render generation of the query resultant.

[0291] FIG. 24Q illustrates an example embodiment of a segment generator 2507 of database system 10. Some or all features and/or functionality of the database system 10 of FIG. 24Q can implement any embodiment of the database system 10 described herein. Some or all features and/or functionality of the segment generator 2507 of FIG. 24Q can implement the segment generator 2507 of FIG. 24P and/or any embodiment of the segment generator 2507 described herein.

[0292] The segment generator 2507 can implement a cluster key-based grouping module 2620 to group records of a dataset 2505 by a predetermined cluster key 2607, which can correspond to one or more columns. The cluster key can be received, accessed in memory, configured via user input, automatically selected based on an optimization, or otherwise determined. This grouping by cluster key can render generation of a plurality of record groups 2625.1-2625.X.

[0293] The segment generator 2507 can implement a columnar rotation module 2630 to generate a plurality of column formatted record data (e.g. column slabs 2610 to be included in respective segments 2424). Each record group 2625 can have a corresponding set of J column-formatted record data 2565.1-2565.J generated, for example, corresponding to J segments in a given segment group.

[0294] A metadata generator module 2640 can further generate parity data, index data, statistical data, and/or other metadata to be included in segments in conjunction with the column-formatted record data. A set of X segment groups corresponding to the X record groups can be generated and stored in database storage 2450. For example, each segment group includes J segments, where parity data of a proper subset of segments in the segment group can be utilized to rebuild column-formatted record data of other segments in the same segment group as discussed previously.

[0295] In some embodiments, the segment generator 2507 implements some or all features and/or functionality of the segment generator disclosed by: U.S. Utility application Ser. No. 16/985,723, entitled “DELAYING SEGMENT GENERATION IN DATABASE SYSTEMS”, filed Aug. 5, 2020, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 16/985,957 entitled “PARALLELIZED SEGMENT GENERATION VIA KEY-BASED SUBDIVISION IN DATABASE SYSTEMS”, filed Aug. 5, 2020, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 16/985,930, entitled “RECORD DEDUPLICATION IN DATABASE SYSTEMS”, filed Aug. 5, 2020, issued as U.S. Pat. No. 11,321,288 on May 3, 2022, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes. For example, the database system 10 implements some or all features and/or functionality of record processing and storage system of U.S. Utility application Ser. No. 16/985,723, U.S. Utility application Ser. No. 16/985,957, and/or U.S. Utility application Ser. No. 16/985,930.

[0296] FIG. 24R illustrates an embodiment of a query processing system 2510 that implements an IO pipeline generator module 2834 to generate a plurality of IO pipelines 2835.1-2835.R for a corresponding plurality of segments 2424.1-2424.R, where these IO pipelines 2835.1-2835.R are each executed by an IO operator execution module 2840 to facilitate generation of a filtered record set by accessing the corresponding segment. Some or all features and/or functionality of the query processing system 2510 of FIG. 24R can implement any embodiment of query processing system 2510, any embodiment of query execution module 2504, and/or any embodiment of executing a query described herein.

[0297] Each IO pipeline 2835 can be generated based on corresponding segment configuration data 2833 for the corresponding segment 2424, such as secondary indexing data for the segment, statistical data/cardinality data for the segment, compression schemes applied to the column slabs of the segment, or other information denoting how the segment is configured. For example, different segments 2424 have different IO pipelines 2835 generated for a given query based on having different secondary indexing schemes, different statistical data/cardinality data for its values, different compression schemes applied for some of all of the columns of its records, or other differences.

[0298] An IO operator execution module 2840 can execute each respective IO pipeline 2835. For example, the IO operator execution module 2840 is implemented by nodes 37 at the IO level of a corresponding query execution plan 2405, where a node 37 storing a given segment 2424 is responsible for accessing the segment as described previously, and thus executes the IO pipeline for the given segment.

[0299] This execution of IO pipelines 2835 by IO operator execution module 2840 correspond to executing IO operators 2421 of a query operator execution flow 2517. The output of IO operators 2421 can correspond to output of IO operators 2421 and/or output of IO level. This output can correspond to data blocks that are further processed via additional operators 2520, for example, by nodes at inner levels and/or the root level of a corresponding query execution plan.

[0300] Each IO pipeline 2835 can be generated based on pushing some or all filtering down to the IO level, where query predicates are applied via the IO pipeline based on accessing index structures, sourcing values, filtering rows, etc. Each IO pipeline 2835 can be generated to render semantically equivalent application of query predicates, despite differences in how the IO pipeline is arranged/executed for the given segment. For example, an index structure of a first segment is used to identify a set of rows meeting a condition for a corresponding column in a first corresponding IO pipeline while a second segment has its row values sourced and compared to a value to identify which rows meet the condition, for example, based on the first segment having the corresponding column indexed and the second segment not having the corresponding column indexed. As another example, the IO pipeline for a first segment applies a compressed column slab processing element to identify where rows are stored in a compressed column slab and to further facilitate decompression of the rows, while a second segment accesses this column slab directly for the corresponding column based on this column being compressed in the first segment and being uncompressed for the second segment.

[0301] FIG. 24S illustrates an example embodiment of an IO pipeline 2835 that is generated to include one or more index elements 3512, one or more source elements 3014, and/or one or more filter elements 3016. These elements can be arranged in a serialized ordering that includes one or more parallelized paths (e.g. the IO pipeline includes an acyclic directed graph of elements). These elements can implement sourcing and/or filtering of rows based on query predicates 2822 applied to one or more columns, identified by corresponding column identifiers 3041 and corresponding filter parameters 3048. Some or all features and/or functionality of the IO pipeline 2835 and/or IO pipeline generator module 2834 of FIG. 24S can implement the IO pipeline 2835 and/or IO pipeline generator module 2834 of FIG. 24R, and/or any embodiment of IO pipeline 2835, of IO pipeline generator module 2834, or of any query execution via accessing segments described herein.

[0302] In some embodiments, the IO pipeline generator module 2834, IO pipeline 2835, IO operator execution module 2840, and/or any embodiment of IO pipeline generation and/or IO pipeline execution described herein, implements some or all features and/or functionality of the IO pipeline generator module 2834, IO pipeline 2835, IO operator execution module 2840, and/or pushing of filtering and/or other operations to the IO level as disclosed by: U.S. Utility application Ser. No. 17/303,437, entitled “QUERY EXECUTION UTILIZING PROBABILISTIC INDEXING” and filed May 28, 2021; U.S. Utility application Ser. No. 17/450,109, entitled “MISSING DATA-BASED INDEXING IN DATABASE SYSTEMS” and filed Oct. 6, 2021; U.S. Utility application Ser. No. 18/310,177, entitled “OPTIMIZING AN OPERATOR FLOW FOR PERFORMING AGGREGATION VIA A DATABASE SYSTEM” and filed May 1, 2023; U.S. Utility application Ser. No. 18/355,505, entitled “STRUCTURING GEOSPATIAL INDEX DATA FOR ACCESS DURING QUERY EXECUTION VIA A DATABASE SYSTEM” and filed Jul. 20, 2023; and/or U.S. Utility application Ser. No. 18/485,861, entitled “QUERY PROCESSING IN A DATABASE SYSTEM BASED ON APPLYING A DISJUNCTION OF CONJUNCTIVE NORMAL FORM PREDICATES” and filed Oct. 12, 2023; all of which hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0303] FIG. 24T presents an embodiment of a database system 10 that includes a plurality of storage clusters 2535. Storage clusters 2535.1-2535.Z of FIG. 24T can implement some or all features and/or functionality of storage clusters 35-1-35-Z described herein, and/or can implement some or all features and/or functionality of any embodiment of a storage cluster described herein. Some or all features and/or functionality of database system 10 of FIG. 24T can implement any embodiment of database system 10 described herein.

[0304] Each storage cluster 2535 can be implemented via a corresponding plurality of nodes 37. In some embodiments, a given node 37 of database system 10 is optionally included in exactly one storage cluster. In some embodiments, one or more nodes 37 of database system 10 are optionally included in no storage clusters (e.g. aren't configured to store segments). In some embodiments, one or more nodes 37 of database system 10 can be included in multiple storage clusters.

[0305] In some embodiments, some or all nodes 37 in a storage cluster 2535 participate at the IO level 2416 in query execution plans based on storing segments 2424 in corresponding memory drives 2425, and based on accessing these segments 2424 during query execution. This can include executing corresponding IO operators, for example, via executing an IO pipeline 2835 (and/or multiple IO pipelines 2835, where each IO pipeline is configured for each respective segment 2424). All segments in a given same segment group (e.g. a set of segments collectively storing parity data and/or replicated parts enabling any given segment in the segment group to be rebuilt/accessed as a virtual segment during query execution via access to some or all other segments in the same segment group as described previously) are optionally guaranteed to be stored in a same storage cluster 2535, where segment rebuilds and/or virtual segment use in query execution can thus be facilitated via communication between nodes in a given storage cluster 2535 accordingly, for example, in response to a node failing and/or a segment becoming unavailable.

[0306] Each storage cluster 2535 can further mediate cluster state data 3105 in accordance with a consensus protocol mediated via the plurality of nodes 37 of the given storage cluster. Cluster state data 3105 can implement any embodiment of state data and/or system metadata described herein. In some embodiments, cluster state data 3105 can indicate data ownership information indicating ownership of each segments stored by the cluster by exactly one node (e.g. as a physical segment or a virtual segment) to ensure queries are executed correctly via processing rows in each segment (e.g. of a given dataset against which the query is executed) exactly once.

[0307] Consensus protocol 3100 can be implemented via the raft consensus protocol and/or any other consensus protocol. Consensus protocol 3100 can be implemented be based on distributing a state machine across a plurality of nodes, ensuring that each node in the cluster agrees upon the same series of state transitions and/or ensuring that each node operates in accordance with the currently agreed upon state transition. Consensus protocol 3100 can implement any embodiment of consensus protocol described herein.

[0308] Coordination across different storage clusters 2535 can be minimal and/or non-existent, for example, based on each storage cluster coordinating state data and/or corresponding query execution separately. For example, state data 3105 across different storage clusters is optionally unrelated.

[0309] Each storage cluster's nodes 37 can perform various database tasks (e.g. participate in query execution) based on accessing/utilizing the state data 3105 of its given storage cluster, for example, without knowledge of state data of other storage clusters. This can include nodes syncing state data 3105 and/or otherwise utilizing the most recent version of state data 3105, for example, based on receiving updates from a leader node in the cluster, triggering a sync process in response to determining to perform a corresponding task requiring most recent state data, accessing/updating a locally stored copy of the state data, and/or otherwise determining updated state data.

[0310] In some embodiments, updating of state data (such as configuration data, system metadata, data shared via a consensus protocol, and/or any other state data described herein), for example, utilized by nodes to perform respective functionality over time, can be performed in conjunction with an event driven model. In some embodiments, such updating of state data over time can be performed in a same or similar fashion as updating of configuration data as disclosed by: U.S. Utility application Ser. No. 18/321,212, entitled COMMUNICATING UPDATES TO SYSTEM METADATA VIA A DATABASE SYSTEM, filed May 22, 2023; and/or U.S. Utility application Ser. No. 18/310,262, entitled “GENERATING A SEGMENT REBUILD PLAN VIA A NODE OF A DATABASE”, filed May 1, 2023; which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0311] In some embodiments, system metadata can be generated and/or updated over time with different corresponding metadata sequence numbers (MSNs). For example, such generation/updating of metadata over time can be implemented via any features and/or functionality of the generation of data ownership information over time with corresponding OSNs as disclosed by U.S. Utility application Ser. No. 16/778,194, entitled “SERVICING CONCURRENT QUERIES VIA VIRTUAL SEGMENT RECOVERY”, filed Jan. 31, 2020, and issued as U.S. Pat. No. 11,061,910 on Jul. 13, 2021, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes. In some embodiments, the system metadata management system 2702 and/or a corresponding metadata system protocol can be implemented via a consensus protocols mediated via a plurality of nodes, for example, to update system metadata 2710, in a via any features and/or functionality of the execution of consensus protocols mediated via a plurality of nodes as disclosed by this U.S. Utility application Ser. No. 16/778,194. In some embodiments, each version of system metadata 2710 can assign nodes to different tasks and/or functionality via any features and/or functionality of assigning nodes to different segments for access in query execution in different versions of data ownership information as disclosed by this U.S. Utility application Ser. No. 16/778,194. In some embodiments, system metadata indicates a current version of data ownership information, where nodes utilize system metadata and corresponding system configuration data to determine their own ownership of segments for use in query execution accordingly, and/or to execute queries utilizing correct sets of segments accordingly, based on processing the denoted data ownership information as U.S. Utility application Ser. No. 16/778,194.

[0312] FIGS. 24U and 24V illustrate embodiments of a database system 10 that utilizes a dictionary structure to store compressed columns. Some or all features and/or functionality of the dictionary structure 5016 of FIGS. 24U and/or 24V can implement any compression scheme data and/or means of generating and/or accessing compressed columns described herein. Any other features and/or functionality of database system 10 of FIG. 24U and/or 24V can implement any other embodiment of database system 10 described herein.

[0313] In some embodiments, columns are compressed as compressed columns 5005 based on a globally maintained dictionary (e.g. dictionary structure 5016), for example, in conjunction with applying Global Dictionary Compression (GDC). Applying Global Dictionary Compression can include replaces variable length column values with fixed length integers on disk (e.g. in database storage 2450), where the globally maintained dictionary is stored elsewhere, for example, via different (e.g. slower/less efficient) memory resources of a different type/in a different location from the database storage 2450 that stores the compressed columns 5005 accessed during query execution.

[0314] The dictionary structure can store a plurality of fixed-length, compressed values 5013 (e.g. integers) each mapped to a single uncompressed value 5012 (e.g. variable-length values, such as strings). The mapping of compressed values 5013 to uncompressed values 5012 can be in accordance with a one-to-one mapping. The mapping of compressed values 5013 to uncompressed values 5012 can be based on utilizing the fixed-length values 5013 as keys of a corresponding map and/or dictionary data structure, and/or can be based on utilizing the uncompressed values 5012 as keys of a corresponding map and/or dictionary data structure.

[0315] A given uncompressed value 5012 that is included in many rows of one or more tables can be replaced (i.e. “compressed”) via a same corresponding compressed value 5013 mapped to this uncompressed value 5012 as the compressed value 5008 for these rows in compressed column 5005 in database storage. As new rows are received for storage over time, their column values for one or more compressed columns 5005 can be replaced via corresponding compressed values 5008 based on accessing the dictionary structure and determining whether the uncompressed value 5012 of this column is stored in the dictionary structure 5016. If yes, the compressed value 5013 mapped to the uncompressed value 5012 in this existing entry is stored as compressed value 5008 in the compressed column 5005 in the database storage 2450. If no, the dictionary structure 5016 can be updated to include a new entry that includes the uncompressed value 5012 and a new compressed value 5013 (e.g. different from all existing compressed values in the structure) generated for this uncompressed value 5012, where this new compressed value 5013 is stored as is applied as compressed value 5008 in the database storage 2450.

[0316] The dictionary structure 5016 can be stored in dictionary storage resources 2514, which can be different types of resources from and/or can be stored in a different location from the database storage 2450 storing the compressed columns for query execution. In some embodiments, the dictionary storage resources 2514 storing dictionary structure 5016 can be considered a portion/type of memory as of database storage 2450 that are accessed during query execution as necessary for decompressing column values. In some embodiments, the dictionary storage resources 2514 storing dictionary structure 5016 can be implemented as metadata storage resources, for example, implemented by a metadata consensus state mediated via a metadata storage cluster of nodes maintaining system metadata such as GDC structures of the database system 10.

[0317] The dictionary structure 5016 can correspond to a given column 5005, where different columns optionally have their own dictionary structure 5016 build and maintained. Alternatively, a common dictionary structure 5016 can optionally be maintained for multiple columns of a same table/same dataset, and/or for multiple columns across different tables/different datasets. For example, a given uncompressed value 5012 appearing in different columns 5005 of the same or different table is compressed via the same fixed-length value 5013 as dictated by the dictionary structure 5016.

[0318] This dictionary structure 5016 can be globally maintained (e.g. across some or all nodes, indicating fixed length values mapped across one or more segments stored in conjunction with storing one or more relational database tables) and can be updated overtime (e.g. as more data is added with new variable length values requiring mapping to fixed length values). For example, the dictionary structure 5016 is maintained/stored in state data that is mediated/accessible by some or all nodes 37 of the database system 10 via the dictionary structure 5016 being included in any embodiment of state data described herein.

[0319] In some embodiments, dictionary compression via dictionary structure 5016 can implement the compression scheme utilized to generate (e.g. compress/decompress the values of) compressed columns 5005 of FIG. 24U based on implementing some or all features and/or functionality of the compression of data during ingress via a dictionary as disclosed by U.S. Utility application Ser. No. 16/985,723, entitled “DELAYING SEGMENT GENERATION IN DATABASE SYSTEMS”, filed Aug. 5, 2020, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0320] In some embodiments, dictionary compression via dictionary structure 5016 can implement the compression scheme utilized to generate (e.g. compress/decompress the values of) compressed columns 5005 of FIG. 24U based on implementing some or all features and/or functionality of global dictionary compression as disclosed by U.S. Utility application Ser. No. 16/220,454, entitled “DATA SET COMPRESSION WITHIN A DATABASE SYSTEM”, filed Dec. 14, 2018, issued as U.S. Pat. No. 11,256,696 on Feb. 22, 2022, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0321] In some embodiments, dictionary compression via dictionary structure 5016 can be utilized in performing GDC join processes during query execution to enable recovery of uncompressed values during query execution, for example, based on implementing some or all features and/or functionality of GDC joins as disclosed by U.S. Utility application Ser. No. 18/226,525, entitled “SWITCHING MODES OF OPERATION OF A ROW DISPERSAL OPERATION DURING QUERY EXECUTION”, filed Jul. 26, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0322] FIG. 24U illustrates an embodiment of database system 10 where a compressed column filter conversion module 5010 accesses a dictionary structure 5016 to generate an updated filtering expression 5021 in conjunction with query execution.

[0323] The compressed column filter conversion module 5010 can generate updated filtering expression 5021 based on updating one or more literals 5011.1 from corresponding literals 5011.0 based on replacing uncompressed values 5012 with compressed values 5013 mapped to these compressed values based on accessing dictionary structure 5016 and determining which fixed-length compressed value 5013 is mapped to each given uncompressed value 5012. Such functionality can be implemented for one or more queries executed by database system 10 to reduce access to the dictionary structure during query execution in conjunction with performing one or more optimizations of the query operator execution flow to improve query performance.

[0324] FIG. 24V illustrates an embodiment of executing a join process 2530 that is implemented as a global dictionary compression (GDC) join. This can include applying a matching row determination module 2558 via access to a dictionary structure 5016,

[0325] In some embodiments, unlike hash maps generated during query execution for access in conjunction with executing other types of JOIN operations (e.g. as described in U.S. Utility application Ser. No. 18/266,525), the dictionary structure 5016 can optionally be accessed during GDC join processes based on being globally maintained, and thus being generated prior to execution of the corresponding query. In particular, the dictionary structure 5016 can be implemented in conjunction with compressing one or more columns, such as a variable length values stored in one or more variable length columns, by mapping these variable length, uncompressed values (e.g. strings, other large values of a given column) to corresponding fixed-length, compressed values 5013 (e.g. integers or other fixed length values).

[0326] For example, segments can store the fixed length values to improve storage efficiency and/or queries can access and process these fixed length values, where the uncompressed variable length values are only required via access to dictionary structure 5016 to emit an uncompressed value 5012 for a given fixed-length value 5013 of a given input row. This functionality can be achieved via performing a corresponding join as described herein, where the matching condition 2519 is implemented for a compressed column and indicates matching by the value of the compressed column, such as simply emitting the uncompressed value mapped to the compressed column as the right output value 2563 for a given input row, implemented as a left input row 2542 of a join operation.

[0327] FIG. 24W illustrates an embodiment of database system 10 operable to communicate with a plurality of user entities. Some or all features and/or functionality of FIG. 24W can implement any embodiment of database system 10 described herein.

[0328] Various users can send data to and/or receive data from database system 10 over time, for example, as corresponding requests and/or responses. Requests can indicate requests for queries to be executed, requests that include data to be loaded/stored, requests that include configuration data configuring any values/functionality utilized by database system 10 to perform its functionality, data supplied in response to a request from database system 10, and/or other requests to database system 10 for processing by database system 10. Responses can indicate query resultants of executed queries, notifications/confirmation that requests were processed successfully or rendered failure, error notifications, data supplied in response to a request from user entity 2012, and/or other information.

[0329] Some or all user entities 2012 can be implemented as user entities corresponding to humans that communicate with database system 10 (e.g. requests are configured via user input to a corresponding computing device of database system 10 or communicating with database system 10); user entities corresponding to groups of multiple people, for example, corresponding to companies/establishments that communicate with database system 10; user entities corresponding to automated entities such as one or more computing devices and/or server systems (e.g. implemented via artificial intelligence, machine learning, and/or configured instructions to cause these automated entities to send requests and/or process responses; and/or corresponding to a given person and configured to send/receive data based on user input from a corresponding person); and/or other user entities. Some or all user entities 2012 can be implemented as humans and/or devices included in/associated with database system 10 (e.g. personnel/employees of a service provided by database system 10; computing devices implementing nodes/processing modules of database system 10 that communicate via internal communication resources of database system 10, etc.). Some or all user entities 2012 can be implemented as humans and/or devices external from database system 10 (e.g. humans/companies that are customers of a service provided by database system 10; computing devices external from the computing devices/nodes/processing resources of database system 10 that communicate with database system 10 via a corresponding communication interface, etc.)

[0330] User entities 2012 can include various type of user entities 2012, which can include one or more user entities 2012.A, one or more user entities 2012.B, and/or one or more user entities 2012.C. A given user entity can optionally implement multiple types of user entities 2012 (e.g. a given user entity 2012 operates as both a user entity 2012.A and a user entity 2012.B). Multiple different users (e.g. different people, different devices) can implement a given user entity 2012 (e.g. different employees of a given company implement a given user entity 2012 at different times; different devices associated with a given person or company implement a given user entity 2012 at different times, etc.).

[0331] In some embodiments, some or all user entities 2012 can configure/perform functionality corresponding to workload management (WLM).

[0332] User entities 2012 can include one or more user entities 2012.A.1-2012.A.M corresponding to query requestor user entities 2005.1-2005.M. Query requestor user entities 2005 can send query requests 2914 indicating queries for execution and/or receive query resultants in response 2920. User entities 2012 can optionally be implemented in a same or similar fashion as external requesting entity 2912.

[0333] User entities 2012 can include one or more user entities 2012.B.1-2012.B.S corresponding to database administrator user entities 2006 that request/configure/monitor loading/storage of/access to a corresponding database 1901 that stores a corresponding plurality of database tables 2712.1-2712-T (e.g. database administrator user entities 2006 optionally correspond to data sources that load their data to the system for use in query execution, where this data source sources data included in tables 2712 of a corresponding database 1901).

[0334] For example, in some embodiments, database system 10 can implement database storage 2450 to store various tables 2712 corresponding to multiple different databases 1902.1-1901.S, for example, each sourced by, accessible by, and/or configured via corresponding user entities 2012.B. Different databases 1901 can store same or different types of data, same or different numbers of tables 2712, etc. Some or all user entities 2012.A can correspond to a given database 1901 (e.g. based on being associated with the corresponding data source and/or user entities 2012.B) for example, where these user entities are only allowed to query against the given database 1901.

[0335] User entities 2012 can include one or more user entities 2012.C corresponding to system administrators of the database system 10 that request/configure/monitor loading/storage of/access to databases in query execution and/or otherwise configure/monitor functionality of database system 10 described herein.

[0336] Different user entities can have different corresponding permissions/privileges/access types, for example, indicated in corresponding user permissions data stored by and/or accessible by database system 10. In some embodiments, one or more given user entities can configure permissions of other user entities. Such permissions can configure types of requests that can be sent, restrictions on data included in responses, and/or which data can be accessed (e.g. in loading data and/or requesting data). For example, some user entities 2012.A can be restricted to certain types of queries/query functions be performed, access to only some databases 1902 and/or only some tables 2712, limits on how many queries be executed/how much data be returned, certain levels of query priority, certain service classes of query execution defining corresponding attributes of how queries be executed/how query execution be restricted, etc. As another example, some user entities 2012.B can be restricted to certain types/rates of data loading to a corresponding database 1901, certain permissions regarding how much configuration of database system 10 they can have power over, etc. As another example, different user entities 2012.C can have different permissions regarding how much configuration of database system 10 they can have power over, different functionalities/aspects of database system that they have permissions to configure, etc.

[0337] FIGS. 25A-25C illustrate embodiments of a database system 10 operable to execute queries indicating join expressions based on implementing corresponding join processes via one or more join operators. Some or all features and/or functionality of FIGS. 25A-25C can be utilized to implement the database system 10 of FIGS. 24A-241 when executing queries indicating join expressions. Some or all features and/or functionality of FIGS. 25A-25C can be utilized to implement any embodiment of the database system 10 described herein.

[0338] FIG. 25A illustrates an embodiment of a database system 10 that implements a record processing and storage system 2505. The record processing and storage system 2505 can be operable to generate and store the segments 2424 discussed previously by utilizing a segment generator 2617 to convert sets of row-formatted records 2422 into column-formatted record data 2565. These row-formatted records 2422 can correspond to rows of a database table with populated column values of the table, for example, where each record 2422 corresponds to a single row as illustrated in FIG. 15. For example, the segment generator 2617 can generate the segments 2424 in accordance with the process discussed in conjunction with FIGS. 15-23. The segments 2424 can be generated to include index data 2518, which can include a plurality of index sections such as the index sections 0-X illustrated in FIG. 23. The segments 2424 can optionally be generated to include other metadata, such as the manifest section and/or statistics section illustrated in FIG. 23.

[0339] The generated segments 2424 can be stored in a segment storage system 2508 for access in query executions. For example, the records 2422 can be extracted from generated segments 2424 in various query executions performed by via a query processing system 2502 of the database system 10, for example, as discussed in FIGS. 25A-25D. In particular, the segment storage system 2508 can be implemented by utilizing the memory drives 2425 of a plurality of IO level nodes 37 that are operable to store segments. As discussed previously, nodes 37 at the IO level 2416 can store segments 2424 in their memory drives 2425 as illustrated in FIG. 24C. These nodes can perform IO operations in accordance with query executions by reading rows from these segments 2424 and/or by recovering segments based on receiving segments from other nodes as illustrated in FIG. 24D. The records 2422 can be extracted from the column-formatted record data 2565 for these IO operations of query executions by utilizing the index data 2518 of the corresponding segment 2424.

[0340] To enhance the performance of query executions via access to segments 2424 to read records 2422 in this fashion, the sets of rows included in each segment are ideally clustered well. In the ideal case, rows sharing the same cluster key are stored together in the same segment or same group of segments. For example, rows having matching values of key columns(s) of FIG. 18 utilized to sort the rows into groups for conversion into segments are ideally stored in the same segments. As used herein, a cluster key can be implemented as any one or more columns, such as key columns(s) of FIG. 18, that are utilized to cluster records into segment groups for segment generation. As used herein, more favorable levels of clustering correspond to more rows with same or similar cluster keys being stored in the same segments, while less favorable levels of clustering correspond to less rows with same or similar cluster keys being stored in the same segments. More favorable levels of clustering can achieve more efficient query performance. In particular, query filtering parameters of a given query can specify particular sets of records with particular cluster keys be accessed, and if these records are stored together, fewer segments, memory drives, and/or nodes need to be accessed and/or utilized for the given query.

[0341] These favorable levels of clustering can be hard to achieve when relying upon the incoming ordering of records in record streams 1-L from a set of data sources 2501-1-2501-L. No assumptions can necessarily be made about the clustering, with respect to the cluster key, of rows presented by external sources as they are received in the data stream. For example, the cluster key value of a given row received at a first time t₁ gives no information about the cluster key value of a row received at a second time t₂ after t₁. It would therefore be unideal to frequently generate segments by performing a clustering process to group the most recently received records by cluster key. In particular, because records received within a given time frame from a particular data source may not be related and have many different cluster key values, the resulting record groups utilized to generate segments would render unfavorable levels of clustering.

[0342] To achieve more favorable levels of clustering, the record processing and storage system 2505 implements a page generator 2511 and a page storage system 2506 to store a plurality of pages 2515. The page generator 2511 is operable to generate pages 2515 from incoming records 2422 of record streams 1-L, for example, as is discussed in further detail in conjunction with FIG. 25C. Each page 2515 generated by the page generator 2511 can include a set of records, for example, in their original row format and/or in a data format as received from data sources 2501-1-2501-L. Once generated, the pages 2515 can be stored in a page storage system 2506, which can be implemented via memory drives and/or cache memory of one or more computing devices 18, such as some or all of the same or different nodes 37 storing segments 2424 as part of the segment storage system 2508.

[0343] This generation and storage of pages 2515 stored by can serve as temporary storage of the incoming records as they await conversion into segments 2424. Pages 2515 can be generated and stored over lengthy periods of time, such as hours or days. During this length time frame, pages 2515 can continue to be accumulated as one or more record streams of incoming records 1-L continue to supply additional records for storage by the database system.

[0344] The plurality of pages generated and stored over this period of time can be converted into segments, for example once a sufficient amount of records have been received and stored as pages, and/or once the page storage system 2506 runs out of memory resources to store any additional pages. It can be advantageous to accumulate and store as many records as possible in pages 2515 prior to conversion to achieve more favorable levels of clustering. In particular, performing a clustering process upon a greater numbers of records, such as the greatest number of records possible can achieve more favorable levels of clustering, For example, greater numbers of records with common cluster keys are expected to be included in the total set of pages 2515 of the page storage system 2506 when the page storage system 2506 accumulates pages over longer periods of time to include a greater number of pages. In other words, delaying the grouping of rows into segments as long as possible increases the chances of having sufficient numbers of records with same and/or similar cluster keys to group together in segments. Determining when to generate segments such that the conversion from pages into segments is delayed as long as possible, and/or such that a sufficient amount of records are converted all at once to induce more favorable levels of cluster, is discussed in further detail in conjunction with FIGS. 26A-26D. Alternatively, the conversion of pages into segments can occur at any frequency, for example, where pages are converted into segments more frequently and/or in accordance with any schedule or determination in other embodiments of the record processing and storage system 2505.

[0345] This mechanism of improving clustering levels in segment generation by delaying the clustering process required for segment generation as long as possible can be further leveraged to reduce resource utilization of the record processing and storage system 2505. As the record processing and storage system 2505 is responsible for receiving records streams from data sources for storage, for example, in the scale of terabyte per second load rates, this process of generating pages from the record streams should therefore be as efficient as possible. The page generator 2511 can be further implemented to reduce resource consumption of the record processing and storage system 2505 in page generation and storage by minimizing the processing of, movement of, and/or access to records 2422 of pages 2515 once generated as they await conversion into segments.

[0346] To reduce the processing induced upon the record processing and storage system 2505 during this data ingress, sets of incoming records 2422 can be included in a corresponding page 2515 without performing any clustering or sorting. For example, as clustering assumptions cannot be made for incoming data, incoming rows can be placed into pages based on the order that they are received and/or based on any order that best conserves resources. In some embodiments, the entire clustering process is performed by the segment generator 2617 upon all stored pages all at once, where the page generator 2511 does not perform any stages of the clustering process.

[0347] In some embodiments, to further reduce the processing induced upon the record processing and storage system 2505 during this data ingress, incoming record data of data streams 1-L undergo minimal reformatting by the page generator 2511 in generating pages 2515. In some cases, the incoming data of record streams 1-L is not reformatted and is simply “placed” into a corresponding page 2515. For example, a set of records are included in given page in accordance with formatted row data received from data sources.

[0348] While delaying segment generation in this fashion improves clustering and further improves ingress efficiency, it can be unideal to wait for records to be processed into segments before they appear in query results, particularly because the most recent data may be of the most interest to end users requesting queries. The record processing and storage system 2505 can resolve this problem by being further operable to facilitate page reads in addition to segment reads in facilitating query executions.

[0349] As illustrated in FIG. 25A, a query processing system 2502 can implement a query execution plan generator module 2503 to generate query execution plan data based on a received query request. The query execution plan data can be relayed to nodes participating in the corresponding query execution plan 2405 indicated by the query execution plan data, for example, as discussed in conjunction with FIG. 24A. A query execution module 2504 can be implemented via a plurality of nodes participating in the query execution plan 2405, for example, where data blocks are propagated upwards from nodes at IO level 2416 to a root node at root level 2412 to generate a query resultant. The nodes at IO level 2416 can perform row reads to read records 2422 from segments 2424 as discussed previously and as illustrated in FIG. 24C. The nodes at IO level 2416 can further perform row reads to read records 2422 from pages 2515. For example, once records 2422 are durably stored by being stored in a page 2515, and/or by being duplicated and stored in multiple pages 2515, the record 2422 can be available to service queries, and will be accessed by nodes 37 at IO level 2416 in executing queries accordingly. This enables the availability of records 2422 for query executions more quickly, where the records need not be processed for storage in their final storage format as segments 2424 to be accessed in query requests. Execution of a given query can include utilizing a set of records stored in a combination of pages 2515 and segments 2424. An embodiment of an IO level node that stores and accesses both segments and pages is illustrated in FIG. 25E.

[0350] The record processing and storage system 2505 can be implemented utilizing the parallelized data input sub-system 11 and/or the parallelized ingress sub-system 24 of FIG. 4. The record processing and storage system 2505 can alternatively or additionally be implemented utilizing the parallelized data store, retrieve, and/or process sub-system 12 of FIG. 6. The record processing and storage system 2505 can alternatively or additionally be implemented by utilizing one or more computing devices 18 and/or by utilizing one or more nodes 37.

[0351] The record processing and storage system 2505 can be otherwise implemented utilizing at least one processor and at least one memory. For example, the at least one memory can store operational instructions that, when executed by the at least one processor, cause the record processing and storage system to perform some or all of the functionality described herein, such as some or all of the functionality of the page generator 2511 and/or of the segment generator 2617 discussed herein. In some cases, one or more individual nodes 37 and/or one or more individual processing core resources 48 can be operable to perform some or all of the functionality of the record processing and storage system 2505, such as some or all of the functionality of the page generator 2511 and/or of the segment generator 2617, independently or in tandem by utilizing their own processing resources and/or memory resources.

[0352] The query processing system 2502 can be alternatively or additionally implemented utilizing the parallelized query and results sub-system 13 of FIG. 5. The query processing system 2502 can be alternatively or additionally implemented utilizing the parallelized data store, retrieve, and/or process sub-system 12 of FIG. 6. The query processing system 2502 can alternatively or additionally be implemented by utilizing one or more computing devices 18 and/or by utilizing one or more nodes 37.

[0353] The query processing system 2502 can be otherwise implemented utilizing at least one processor and at least one memory. For example, the at least one memory can store operational instructions that, when executed by the at least one processor, cause the record processing and storage system to perform some or all of the functionality described herein, such as some or all of the functionality of the query execution plan generator module 2503 and/or of the query execution module 2504 discussed herein. In some cases, one or more individual nodes 37 and/or one or more individual processing core resources 48 can be operable to perform some or all of the functionality of the query processing system 2502, such as some or all of the functionality of query execution plan generator module 2503 and/or of the query execution module 2504, independently or in tandem by utilizing their own processing resources and/or memory resources.

[0354] In some embodiments, one or more nodes 37 of the database system 10 as discussed herein can be operable to perform multiple functionalities of the database system 10 illustrated in FIG. 25A. For example, a single node can be utilized to implement the page generator 2511, the page storage system 2506, the segment generator 2617, the segment storage system 2508, the query execution plan generator module, and/or the query execution module 2504 as a node 37 at one or more levels 2410 of a query execution plan 2405. In particular, the single node can utilize different processing core resources 48 to implement different functionalities in parallel, and/or can utilize the same processing core resources 48 to implement different functionalities at different times.

[0355] Some or all data sources 2501 can implemented utilizing at least one processor and at least one memory. Some or all data sources 2501 can be external from database system 10 and/or can be included as part of database system 10. For example, the at least one memory of a data source 2501 can store operational instructions that, when executed by the at least one processor of the data source 2501, cause the data source 2501 to perform some or all of the functionality of data sources 2501 described herein. In some cases, data sources 2501 can receive application data from the database system 10 for download, storage, and/or installation. Execution of the stored application data by processing modules of data sources 2501 can cause the data sources 2501 to execute some or all of the functionality of data sources 2501 discussed herein.

[0356] In some embodiments, system communication resources 14, external network(s) 17, local communication resources 25, wide area networks 22, and/or other communication resources of database system 10 can be utilized to facilitate any transfer of data by the record processing and storage system 2505. This can include, for example: transmission of record streams 1-L from data sources 2501 to the record processing and storage system 2505; transfer of pages 2515 to page storage system 2506 once generated by the page generator 2511; access to pages 2515 by the segment generator 2617; transfer of segments 2424 to the segment storage system 2508 once generated by the segment generator 2617; communication of query execution plan data to the query execution module 2504, such as the plurality of nodes 37 of the corresponding query execution plan 2405; reading of records by the query execution module 2504, such as IO level nodes 37, via access to pages 2515 stored page storage system 2506 and/or via access to segments 2424 stored segment storage system 2508; sending of data blocks generated by nodes 37 of the corresponding query execution plan 2405 to other nodes 37 in conjunction with their execution of the query; and/or any other accessing of data, communication of data, and/or transfer of data by record processing and storage system 2505 and/or within the record processing and storage system 2505 as discussed herein.

[0357] The record processing and storage system 2505 and/or the query processing system 2502 of FIG. 25A, and/or any other embodiment of record processing and storage system 2505 and/or the query processing system 2502 described herein, can be implemented at a massive scale, for example, by being implemented by a database system 10 that is operable to receive, store, and perform queries against a massive number of records of one or more datasets, such as millions, billions, and/or trillions of records stored as many Terabytes, Petabytes, and/or Exabytes of data as discussed previously. In particular, the record processing and storage system 2505 and/or the query processing system 2502 can each be implemented by a large number, such as hundreds, thousands, and/or millions of computing devices 18, nodes 37, and/or processing core resources 48 that perform independent processes in parallel, for example, with minimal or no coordination, to implement some or all of the features and/or functionality of the record processing and storage system 2505 and/or the query processing system 2502 at a massive scale.

[0358] Some or all functionality performed by the record processing and storage system 2505 and/or the query processing system 2502 as described herein cannot practically be performed by the human mind, particularly when the database system 10 is implemented to store and perform queries against records at a massive scale as discussed previously. In particular, the human mind is not equipped to perform record processing, record storage, and/or query execution for millions, billions, and/or trillions of records stored as many Terabytes, Petabytes, and/or Exabytes of data. Furthermore, the human mind is not equipped to distribute and perform record processing, record storage, and/or query execution as multiple independent processes, such as hundreds, thousands, and/or millions of independent processes, in parallel and/or within overlapping time spans.

[0359] Some or all features and/or functionality of FIG. 25A can be performed via at least one node 37 in conjunction with system metadata, applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 25A based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data, and/or based on further accessing and/or executing this configuration data to implement some or all functionality of the record processing storage system and/or to implement some or all functionality of the query processing system as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 25A can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 25A can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0360] FIG. 25B illustrates an example embodiment of the record processing and storage system 2505 of FIG. 25A.

[0361] Some or all of the features illustrated and discussed in conjunction with the record processing and storage system 2505 FIG. 25B can be utilized to implement the record processing and storage system 2505 and/or any other embodiment of the record processing and storage system 2505 described herein.

[0362] The record processing and storage system 2505 can include a plurality of loading modules 2510-1-2510-N. Each loading module 2510 can be implemented via its own processing and/or memory resources. For example, each loading module 2510 can be implemented via its own computing device 18, via its own node 37, and/or via its own processing core resource 48. The plurality of loading modules 2510-1-2510-N can be implemented to perform some or all of the functionality of the record processing and storage system 2505 in a parallelized fashion.

[0363] The record processing and storage system 2505 can include queue reader 2559, a plurality of stateful file readers 2556-1-2556-N, and/or stand-alone file readers 2558-1-2558-N. For example, the queue reader 2559, a plurality of stateful file readers 2556-1-2556-N, and/or stand-alone file readers 2558-1-2558-N are utilized to enable each loading modules 2510 to receive one or more of the record streams 1-L received from the data sources 2501-1-2501-L as illustrated in FIG. 25A. For example, each loading module 2510 receives a distinct subset of the entire set of records received by the record processing and storage system 2505 at a given time.

[0364] Each loading module 2510 can receive records 2422 in one or more record streams via its own stateful file reader 2556 and/or stand-alone file reader 2558. Each loading module 2510 can optionally receive records 2422 and/or otherwise communicate with a common queue reader 2559. Each stateful file reader 2556 can communicate with a metadata cluster 2552 that includes data supplied by and/or corresponding to a plurality of administrators 2554-1-2554-M. The metadata cluster 2552 can be implemented by utilizing the administrative processing sub-system 15 and/or the configuration sub-system 16. The queue reader 2559, each stateful file reader 2556, and/or each stand-alone file reader 2558 can be implemented utilizing the parallelized ingress sub-system 24 and/or the parallelized data input sub-system 11. The metadata cluster 2552, the queue reader 2559, each stateful file reader 2556, and/or each stand-alone file reader 2558 can be implemented utilizing at least one computing device 18 and/or at least one node 37. In cases where a given loading module 2510 is implemented via its own computing device 18 and/or node 37, the same computing device 18 and/or node 37 can optionally be utilized to implement the stateful file reader 2556, and/or each stand-alone file reader 2558 communicating with the given loading module 2510.

[0365] Each loading module 2510 can implement its own page generator 2511, its own index generator 2513, and/or its own segment generator 2617, for example, by utilizing its own processing and/or memory resources such as the processing and/or memory resources of a corresponding computing device 18. For example, the page generator 2511 of FIG. 25A can be implemented as a plurality of page generators 2511 of a corresponding plurality of loading modules 2510 as illustrated in FIG. 25B. Each page generator 2511 of FIG. 25B can process its own incoming records 2422 to generate its own corresponding pages 2515.

[0366] As pages 2515 are generated by the page generator 2511 of a loading module 2510, they can be stored in a page cache 2512. The page cache 2512 can be implemented utilizing memory resources of the loading module 2510, such as memory resources of the corresponding computing device 18. For example, the page cache 2512 of each loading module 2010-1-2010-N can individually or collectively implement some or all of the page storage system 2506 of FIG. 25A.

[0367] The segment generator 2617 of FIG. 25A can similarly be implemented as a plurality of segment generators 2617 of a corresponding plurality of loading modules 2510 as illustrated in FIG. 25B. Each segment generator 2617 of FIG. 25B can generate its own set of segments 2424-1-2424-J included in one or more segment groups 2622. The segment group 2622 can be implemented as the segment group of FIG. 23, for example, where J is equal to five or another number of segments configured to be included in a segment group. In particular, J can be based on the redundancy storage encoding scheme utilized to generate the set of segments and/or to generate the corresponding parity data 2426.

[0368] The segment generator 2617 of a loading module 2510 can access the page cache 2512 of the loading module 2510 to convert the pages 2515 previously generated by the page generator 2511 into segments. In some cases, each segment generator 2617 requires access to all pages 2515 generated by the segment generator 2617 since the last conversion process of pages into segments. The page cache 2512 can optionally store all pages generated by the page generator 2511 since the last conversion process, where the segment generator 2617 accesses all of these pages generated since the last conversion process to cluster records into groups and generate segments. For example, the page cache 2512 is implemented as a write-through cache to enable all previously generated pages since the last conversion process to be accessed by the segment generator 2617 once the conversion process commences.

[0369] In some cases, each loading module 2510 implements its segment generator 2617 upon only the set of pages 2515 that were generated by its own page generator 2511, accessible via its own page cache 2512. In such cases, the record grouping via clustering key to create segments with the same or similar cluster keys are separately performed by each segment generator 2617 independently without coordination, where this record grouping via clustering key is performed on N distinct sets of records stored in the N distinct sets of pages generated by the N distinct page generators 2511 of the N distinct loading modules 2510. In such cases, despite records never being shared between loading modules 2510 to further improve clustering, the level of clustering of the resulting segments generated independently by each loading module 2510 on its own data is sufficient, for example, due to the number of records in each loading module's 2510 set of pages 2515 for conversion being sufficiently large to attain favorable levels of clustering.

[0370] In such embodiments, each loading modules 2510 can independently initiate its own conversion process of pages 2515 into segments 2424 by waiting as long as possible based on its own resource utilization, such as memory availability of its page cache 2512. Different segment generators 2617 of the different loading modules 2510 can thus perform their own conversion of the corresponding set of pages 2515 into segments 2424 at different times, based on when each loading modules 2510 independently determines to initiate the conversion process, for example, based on each independently making the determination to generate segments as discussed in conjunction with FIG. 26A. Thus, as discussed herein, the conversion process of pages into segments can correspond to a single loading module 2510 converting all of its pages 2515 generated by its own page generator 2511 since its own last the conversion process into segments 2424, where different loading modules 2510 can initiate and execute this conversion process at different times and/or with different frequency.

[0371] In other cases, it is ideal for even more favorable levels of clustering to be attained via sharing of all pages for conversion across all loading modules 2510. In such cases, a collective decision to initiate the conversion process can be made across some or all loading modules 2510, for example, based on resource utilization across all loading modules 2510. The conversion process can include sharing of and/or access to all pages 2515 generated via the process, where each segment generator 2617 accesses records in some or all pages 2515 generated by and/or stored by some or all other loading modules 2510 to perform the record grouping by cluster key. As the full set of records is utilized for this clustering instead of N distinct sets of records, the levels of clustering in resulting segments can be further improved in such embodiments. This improved level of clustering can offset the increased page movement and coordination required to facilitate page access across multiple loading modules 2510. As discussed herein, the conversion process of pages into segments can optionally correspond to multiple loading modules 2510 converting all of their collectively generated pages 2515 since their last conversion process into segments 2424 via sharing of their generated pages 2515.

[0372] An index generator 2513 can optionally be implemented by some or all loading modules 2510 to generate index data 2516 for some or all pages 2515 prior to their conversion into segments. The index data 2516 generated for a given page 2515 can be appended to the given page, can be stored as metadata of the given page 2515, and/or can otherwise be mapped to the given page 2515. The index data 2516 for a given page 2515 correspond to page metadata, for example, indexing records included in the corresponding page. As a particular example, the index data 2516 can include some or all of the data of index data 2518 generated for segments 2424 as discussed previously, such as index sections 0-x of FIG. 23. As another example, the index data 2516 can include indexing information utilized to determine the memory location of particular records and/or particular columns within the corresponding page 2515.

[0373] In some cases, the index data 2516 can be generated to enable corresponding pages 2515 to be processed by query IO operators utilized to read rows from pages, for example, in a same or similar fashion as index data 2518 is utilized to read rows from segments. In some cases, index probing operations can be utilized by and/or integrated within query IO operators to filter the set of rows returned in reading a page 2515 based on its index data 2516 and/or to filter the set of rows returned in reading a segment 2424 based on its index data 2518.

[0374] In some cases, index data 2516 is generated by index generator 2513 for all pages 2515, for example, as each page 2515 is generated, or at some point after each page 2515 is generated. In other cases, index data 2516 is only generated for some pages 2515, for example, where some pages do not have index data 2516 as illustrated in FIG. 25B. For example, some pages 2515 may never have corresponding index data 2516 generated prior to their conversion into segments. In some cases, index data 2516 is generated for a given page 2515 with its records are to be read in execution of a query by the query processing system 2502. For example, a node 37 at IO level 2416 can be implemented as a loading module 2510 and can utilize its index generator 2513 to generate index data 2516 for a particular page 2515 in response to having query execution plan data indicating that records 2422 be read the particular page from the page cache 2512 of the loading module in conjunction with execution of a query. The index data 2516 can be optionally stored temporarily for the life of the given query to facilitate reading of rows from the corresponding page for the given query only. The index data 2516 alternatively be stored as metadata of the page 2515 once generated, as illustrated in FIG. 25B. This enables the previously generated index data 2516 of a given page to be utilized in subsequent queries requiring reads from the given page.

[0375] As illustrated in FIG. 25B, each loading modules 2510 can generate and send pages 2515, corresponding index data 2516, and/or segments 2424 to long term storage 2540-1-2540-J of a particular storage cluster 2535. For example, system communication resources 14 can be utilized to facilitate sending of data from loading modules 2510 to storage cluster 2535 and/or to facilitate sending of data from storage cluster 2535 to loading modules 2510.

[0376] The storage cluster 2535 can be implemented by utilizing a storage cluster 35 of FIG. 6, where each long term storage 2540-1-2540-J is implemented by a corresponding computing device 18-1-18-J and/or by a corresponding node 37-1-37-J. In some cases, each storage cluster 35-1-35-z of FIG. 6 can receive pages 2515, corresponding index data 2516, and/or segments 2424 from its own set of loading modules 2510-1-2510-N, where the record processing and storage system 2505 of FIG. 25B can include z sets of loading modules 2510-1-2510-N that each generate pages 2515, segments 2524, and/or index data 2516 for storage in its own corresponding storage cluster 35.

[0377] The processing and/or memory resources utilized to implement each long term storage 2540 can be distinct from the processing and/or memory resources utilized to implement the loading modules 2510. Alternatively, some loading modules can optionally share processing and/or memory resources long term storage 2540, for example, where a same computing device 18 and/or a same node 37 implements a particular long term storage 2540 and also implements a particular loading modules 2510.

[0378] Each loading module 2510 can generate and send the segments 2424 to long term storage 2540-1-2540-J in a set of persistence batches 2532-1-2532-J sent to the set of long term storage 2540-1-2540-J as illustrated in FIG. 25B. For example, upon generating a segment group 2522 of J segments 2424, a loading module 2510 can send each of the J segments in the same segment group to a different one of the set of long term storage 2540-1-2540-J in the storage cluster 2535. For example, a particular long term storage 2540 can generate recovered segments as necessary for processing queries and/or for rebuilding missing segments due to drive failure as illustrated in FIG. 24D, where the value K of FIG. 24D is less than the value J and wherein the nodes 37 of FIG. 24D are utilized to implement the long term storage 2540-1-2540-J.

[0379] As illustrated in FIG. 25B, each persistence batch 2532-1-2532-J can optionally or additionally include pages 2515 and/or their corresponding index data 2516 generated via index generator 2513. Some or all pages 2515 that are generated via a loading module 2510's page generator 2511 can be sent to one or more long term storage 2540-1-2540-J. For example, a particular page 2515 can be included in some or all persistence batches 2532-1-2532-J sent to multiple ones of the set of long term storage 2540-1-2540-J for redundancy storage as replicated pages stored in multiple locations for the purpose of fault tolerance. Some or all pages 2515 can be sent to storage cluster 2535 for storage prior to being converted into segments 2424 via segment generator 2617. Some or all pages 2515 can be stored by storage cluster 2535 until corresponding segments 2424 are generated, where storage cluster 2535 facilitates deletion of these pages from storage in one or more long term storage 2540-1-2540-J once these pages are converted and/or have their records 2422 successfully stored by storage cluster 2535 in segments 2424.

[0380] In some cases, a loading module 2510 maintains storage of pages 2515 via page cache 2512, even if they are sent to storage cluster 2535 in persistence batches 2532. This can enable the segment generator 2617 to efficiently read pages 2515 during the conversion process via reads from this local page cache 2512. This can be ideal in minimizing page movement, as pages do not need to be retrieved from long term storage 2540 for conversion into segments by loading modules 2510 and can instead be locally accessed via maintained storage in page cache 2512. Alternatively, a loading module 2510 removes pages 2515 from storage via page cache 2512 once they are determined to be successfully stored in long term storage 2540. This can be ideal in reducing the memory resources required by loading module 2510 to store pages, as only pages that are not yet durably stored in long term storage 2540 need be stored in page cache 2512.

[0381] Each long term storage 2540 can include its own page storage 2546 that stores received pages 2515 generated by and received from one or more loading modules 2010-1-2010-N, implemented utilizing memory resources of the long term storage 2540. For example, the page storage 2546 of each long term storage 2540-1-2540-J can individually or collectively implement some or all of the page storage system 2506 of FIG. 25A. The page storage 2546 can optionally store index data 2516 mapped to and/or included as metadata of its pages 2515. Each long term storage 2540 can alternatively or additionally include its own segment storage 2548 that stores segments generated by and received from one or more loading modules 2010-1-2010-N. For example, the segment storage 2548 of each long term storage 2540-1-2540-J can individually or collectively implement some or all of the segment storage system 2508 of FIG. 25A.

[0382] The pages 2515 stored in page storage 2546 of long term storage 2540 and/or the segments 2424 stored in segment storage 2548 of long term storage 2540 can be accessed to facilitate execution of queries. As illustrated in FIG. 25B, each long term storage 2540-1-2540-J can perform IO operators 2542 to facilitate reads of records in pages 2515 stored in their page storage 2546 and/or to facilitate reads of records in segments 2424 stored in their segment storage 2548. For example, some or all long term storage 2540-1-2540-J can be implemented as nodes 37 at the IO level 2416 of one or more query execution plans 2405. In particular, the some or all long term storage 2540-1-2540-J can be utilized to implement the query processing system 2502 by facilitating reads to stored records via IO operators 2542 in conjunction with query executions.

[0383] Note that at a given time, a given page 2515 may be stored in the page cache 2512 of the loading module 2510 that generated the given page 2515, and may alternatively or additionally be stored in one or more long term storage 2540 of the storage cluster 2535 based on being sent to the in one or more long term storage 2540. Furthermore, at a given time, a given record may be stored in a particular page 2515 in a page cache 2512 of a loading module 2510, may be stored the particular page 2515 in page storage 2546 of one or more long term storage 2540, and/or may be stored in exactly one particular segment 2424 in segment storage 2548 of one long term storage 2540.

[0384] Because records can be stored in multiple locations of storage cluster 2535, the long term storage 2540 of storage cluster 2535 can be operable to collectively store page and/or segment ownership consensus 2544. This can be useful in dictating which long term storage 2540 is responsible for accessing each given record stored by the storage cluster 2535 via IO operators 2542 in conjunction with query execution. In particular, as a query resultant is only guaranteed to be correct if each required record is accessed exactly once, records reads to a particular record stored in multiple locations could render a query resultant as incorrect. The page and/or segment ownership consensus 2544 can include one or more versions of ownership data, for example, that is generated via execution of a consensus protocol mediated via the set of long term storage 2540-1-2540-J. The page and/or segment ownership consensus 2544 can dictate that every record is owned by exactly one long term storage 2540 via access to either a page 2515 storing the record or a segment 2424 storing the record, but not both. The page and/or segment ownership consensus 2544 can indicate, for each long term storage 2540 in the storage cluster 2535, whether some or all of its pages 2515 or some or all of its segments 2424 are to be accessed in query executions, where each long term storage 2540 only accesses the pages 2515 and segments 2424 indicated in page and/or segment ownership consensus 2544.

[0385] In such cases, all record access for query executions performed by query execution module 2504 via nodes 37 at IO level 2416 can optionally be performed via IO operators 2542 accessing page storage 2546 and/or segment storage 2548 of long term storage 2540, as this access can guarantee reading of records exactly once via the page and/or segment ownership consensus 2544. For example, the long term storage 2540 can be solely responsible for durably storing the records utilized in query executions. In such embodiments, the cached and/or temporary storage of pages and/or segments of loading modules 2510, such as pages 2515 in page caches 2512, are not read for query executions via accesses to storage resources of loading modules 2510.

[0386] Some or all features and/or functionality of FIG. 25B can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 25B based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to implement some or all functionality of a loading module 2510, to implement some or all functionality of a file reader, and/or to implement some or all functionality of the storage cluster 2535 as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 25B can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 25B can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0387] FIG. 25C illustrates an example embodiment of a page generator 2511. The page generator 2511 of FIG. 25C can be utilized to implement the page generator 2511 of FIG. 25A, can be utilized to implement each page generator 2511 of each loading module 2510 of FIG. 25B, and/or can be utilized to implement any embodiments of page generator 2511 described herein.

[0388] A single incoming record stream, or multiple incoming record streams 1-L, can include the incoming records 2422 as a stream of row data 2910. Each row data 2910 can be transmitted as an individual packet and/or a set of packets by the corresponding data source 2501 to include a single record 2422, such as a single row of a database table. Alternatively each row data 2910 can be transmitted by the corresponding data source 2501 as an individual packet and/or a set of packets to include a batched set of multiple records 2422, such as multiple rows of a database table. Row data 2910 received from the same or different data source over time can each include a same number of rows or a different number of rows, and can be sent in accordance with a particular format. Row data 2910 received from the same or different data source over time can include records with the same or different numbers of columns, with the same or different types and/or sizes of data populating its columns, and/or with the same or different row schemas. In some cases, row data 2910 is received in a stream over time for processing by a loading module 2510 via a stateful file reader 2556 and/or via a stand-alone file reader 2558.

[0389] Incoming rows can be stored in a pending row data pool 3410 while they await conversion into pages 2515. The pending row data pool 3410 can be implemented as an ordered queue or an unordered set. The pending row data pool 3410 can be implemented by utilizing storage resources of the record processing and storage system. For example, each loading module 2510 can have its own pending row data pool 3410. Alternatively, multiple loading modules 2510 can access the same pending row data pool 3410 that stores all incoming row data 2910, for example, by utilizing queue reader 2559.

[0390] The page generator 2511 can facilitate parallelized page generation via a plurality of processing core resources 48-1-48-W. For example, each loading module 2510 has its own plurality of processing core resources 48-1-48-W, where the processing core resources 48-1-48-W of a given loading module 2510 is implemented via the set of processing core resources 48 of one or more nodes 37 utilized to implement the given loading module 2510. As another example, the plurality of processing core resources 48-1-48-W are each implemented by a corresponding one of the set of each loading module 2510-1-2510-N, for example, where each loading module 2510-1-2510-N is implemented via its own processing core resources 48-1-48-W.

[0391] Over time, each processing core resource 48 can retrieve and/or can be assigned pending row data 2910 in the pending row data pool 3410. For example, when a given processing core resource 48 has finished another job, such as completed processing of another row data 2910, the processing core resource 48 can fetch a new row data 2910 for processing into a page 2515. For example, the processing core resource 48 retrieves a first ordered row data 2910 from a queue of the pending row data pool 3410, retrieves a highest priority row data 2910 from the pending row data pool 3410, retrieves an oldest row data 2910 from the pending row data pool 3410, and/or retrieves a random row data 2910 from the pending row data pool 3410. Once one processing core resource 48 retrieves and/or otherwise utilizes a particular row data 2910 for processing into a page, the particular row data 2910 is removed from the pending row data pool 3410 and/or is otherwise not available for processing by other processing core resources 48.

[0392] Each processing core resource 48 can generate pages 2515 from the row data received over time. As illustrated in FIG. 25C, the pages 2515 are depicted to include only one row data, such as a single row or multiple rows batched together in the row data 2910. For example, each page is generated directly from corresponding row data 2910. Alternatively, a page 2515 can include multiple row data 2910, for example, in sequence and/or concatenated in the page 2515. The page can include multiple row data 2910 from a single data source 2501 and/or can include multiple row data 2910 from multiple different data sources 2501. For example, the processing core resource 48 can retrieve one row data 2910 from the pending row data pool 3410 at a time, and can append each row data 2910 to a given page until the page 2515 is complete, where the processing core resource 48 appends subsequently retrieved row data 2910 to a new page. Alternatively, the processing core resource 48 can retrieve multiple row data 2910 at once, and can generate a corresponding page 2515 to include this set of multiple row data 2910.

[0393] Once a page 2515 is complete, the corresponding processing core resource 48 can facilitate storage of the page in page storage system 2506. This can include adding the page 2515 to the page cache 2512 of the corresponding loading module 2510. This can include facilitating sending of the page 2515 to one or more long term storage 2540 for storage in corresponding page storage 2546. Different processing core resources 48 can each facilitate storage of the page via common resources, or via designated resources specific to each processing core resources 48, of the page storage system 2506.

[0394] Some or all features and/or functionality of FIG. 25C can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 25C based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to implement some or all functionality of a loading module 2510, to implement some or all functionality of page generator 2511 and/or page storage system 2506 as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 25C can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 25C can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0395] FIG. 25D illustrates an example embodiment of the page storage system 2506. As used herein, the page storage system 2506 can include page cache 2512 of a single loading module 2510; can include page caches 2512 of some or all loading module 2510-1-2510-N; can include page storage 2546 of a single long term storage 2540 of a storage cluster 2535; can include page storage 2546 of some or all long term storage 2540-1-2540-J of a single storage cluster 2535; can include page storage 2546 of some or all long term storage 2540-1-2540-J of multiple different storage clusters, such as some or all storage clusters 35-1-35-z; and/or can include any other memory resources of database system 10 that are utilized to temporarily and/or durably store pages.

[0396] Some or all features and/or functionality of FIG. 25D can be performed via at least one node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where at least one node 37 participates in some or all features and/or functionality of FIG. 25D based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data and/or based on further accessing and/or executing this configuration data to implement some or all functionality of a loading module 2510 and/or a given long term storage 2540 as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 25D can optionally change and/or be updated over time, and/or a set of nodes participating in executing some or all features and/or functionality of FIG. 25D can have changing nodes over time, based on the system metadata applied across the plurality of nodes 37 being updated over time, based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata, and/or based on nodes being added and/or removed from the plurality of nodes over time.

[0397] FIG. 25E illustrates an example embodiment of a node 37 utilized to implement a given long term storage 2540 of FIG. 25B. The node 37 of FIG. 25E can be utilized to implement the node 37 of FIG. 25B, FIG. 25C, 25D, some or all nodes 37 at the IO level 2416 of a query execution plan 2405 of FIG. 24A, and/or any other embodiments of node 37 described herein. As illustrated a given node 37 can have its own segment storage 2548 and/or its own page storage 2546 by utilizing one or more of its own memory drives 2425. Note that while the segment storage 2548 and page storage 2546 are segregated in the depiction of a memory drives 2425, any resources of a given memory drive or set of memory drives can be allocated for and/or otherwise utilized to store either pages 2515 or segments 2424. Optionally, some particular memory drives 2425 and/or particular memory locations within a particular memory drive can be designated for storage of pages 2515, while other particular memory drives 2425 and/or other particular memory locations within a particular memory drive can be designated for storage of segments 2424.

[0398] The node 37 can utilize its query processing module 2435 to access pages and/or records in conjunction with its role in a query execution plan 2405, for example, at the IO level 2416. For example, the query processing module 2435 generates and sends segment read requests to access records stored in segments of segment storage 2548, and/or generates and sends page read requests to access records stored in pages 2515 of page storage 2546. In some cases, in executing a given query, the node 37 reads some records from segments 2424 and reads other records from pages 2515, for example, based on assignment data indicated in the page and/or segment ownership consensus 2544. The query processing module 2435 can generate its data blocks to include the raw row data of the read records and/or can perform other query operators to generate its output data blocks as discussed previously. The data blocks can be sent to another node 37 in the query execution plan 2405 for processing as discussed previously, such as a parent node and/or a node in a shuffle node set within the same level 2410.

[0399] Some or all features and/or functionality of FIG. 25E can be performed a given node 37 in conjunction with system metadata applied across a plurality of nodes 37, for example, where the given node 37 performs some or all features and/or functionality of FIG. 25E based on receiving and storing the system metadata in local memory of the at least one node 37 as configuration data, and/or based on further accessing and/or executing this configuration data to implement some or all functionality of the given node 37 of FIG. 25E as part of its database functionality accordingly. Performance of some or all features and/or functionality of FIG. 25E can optionally change and/or be updated over time based on the system metadata applied across the plurality of nodes 37 being updated over time and/or based on nodes on updating their configuration data stored in local memory to reflect changes in the system metadata based on receiving data indicating these changes to the system metadata.

[0400] In some embodiments, some or all features and/or functionality of loading new data (e.g. as new pages and/or new segments), for example, via one or more loading modules 2510 and/or via record processing and storage system 2505 as described herein implements some or all features and/or functionality of loading modules, record processing and storage system, and/or any loading of data for storage and access in query execution as disclosed by: U.S. Utility application Ser. No. 18/355,497, entitled “TRANSFER OF A SET OF SEGMENTS BETWEEN STORAGE CLUSTERS OF A DATABASE SYSTEM”, filed Jul. 20, 2023; and/or U.S. Utility application Ser. No. 18/308,954, entitled “QUERY EXECUTION DURING STORAGE FORMATTING UPDATES”, filed Apr. 28, 2023; which are hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0401] FIGS. 26A-26H illustrate embodiments of a database system 10 that implements an energy utilization processing system 3500. The embodiments illustrated in 26A-26H can be utilized to implement one or more nodes 37 of one or more computing devices 18 implementing database system 10. Some or all features and/or functionality of FIGS. 26A-26H can be utilized to implement any embodiment of database system 10 described herein.

[0402] In some embodiments, database system 10 can be operable to perform various database operations based on generating and/or processing energy utilization data 3510. In particular, various energy utilization data 3510 can be generated and/or processed to characterize and/or improve energy utilization of database system 10.

[0403] The various computing devices 18 and/or corresponding computing device nodes 37, and/or processing core resources 48, memory drives 2425, disk memory 38, main memory 40, system communication resources 14, and/or any other hardware implementing some or all functionality of database system 10 are delivered power to enable their functionality. For example, the respective computing devices 18 are housed in one or more data centers to which power is supplied, for example, via an electrical grid and/or via one or more other power supply resources.

[0404] Implementing various functionality of database system 10 at a massive scale can induce large amounts of power consumption, which can be costly (e.g. in monetary payments to the data center and/or entity managing the electrical grid) and/or can be harmful to the environment (e.g. due to carbon emissions and/or other greenhouse gas (GHG) emissions required to generate the energy, for example, via the electrical grid, that is consumed by the database system 10 in performing various operations over time at the massive scale. It can therefore be advantageous to characterize energy consumption by the database system and/or to employ various strategies to reduce energy utilization in performing database operations.

[0405] FIGS. 26A-26H present embodiments of database system 10 that improve energy efficiency, for example, via an overall reduction in energy utilization and/or via increase in amount/scale of operations/storage/functionality that is performed per unit of energy utilization. Such improvements can be achieved via implementing some or all features and/or functionality of energy utilization processing system 3500 described herein, and/or via processing and/or generating any embodiment of energy utilization data 3510 described herein. Some or all features and/or functionality presented in FIGS. 26A-26H can improve the technology of database systems based on decreasing energy utilization and/or based on increasing energy efficiency, which can thus decrease monetary cost and/or environmental harm required to perform database functionality, which can be particularly substantial when the database system is implemented at a massive scale.

[0406] FIG. 26A presents an embodiment of database system 10 that implements a data processing and/or storage system 2500 to facilitate storage of data 2711 and/or to facilitate execution of various database system operations 3701 to receive, generate, facilitate persistent storage of (e.g. long term storage of, and/or storage of data over some length of time while withstanding hardware outages via various migration and/or rebuilding as necessary), and/or access this stored data 2711. For example, the data processing and/or storage system 2500 implements any of the various functionality of database system 10 described herein, where execution of one or more database operations 3701 can implement any database functionality described herein and/or where data 2711 corresponds to any data (e.g. any records/rows/relational database tables/datasets) stored by database system 10. Some or all features and/or functionality of database system 10 of FIG. 26A can implement any embodiment of database system 10 described herein.

[0407] The database system 10 can further implement an energy utilization processing system 3500, which can generate, process, and/or communicate energy utilization data 3510. For example, the energy utilization processing system 3500 receives energy utilization data 3510 from data processing and/or storage system 2500 to characterize energy utilization consumed while executing one or more database system operations 3701 and/or while storing data 2711 persistently over time. As another example, the energy utilization processing system 3500 generates energy utilization data 3510 to configure how data processing and/or storage system 2500 executes one or more database system operations 3701 and/or to configure how data processing and/or storage system 2500 stores data 2711, for example, to improve energy efficiency in executing these database system operations 3701 and/or in storing data 2711.

[0408] FIG. 26B presents an embodiment of database system 10 that is implemented via computing hardware 3671 housed in one or more data centers 3670. Some or all features and/or functionality of database system 10 of FIG. 26B can implement any embodiment of database system 10 described herein.

[0409] The one or more data centers 3670 can be physical facilities (e.g. buildings) housing the computing hardware 3671. For example, all data 2711 is stored and/or all operations 3701 are performed via hardware housed in these one or more data centers 3670. The one or more data centers are optionally located in a same geolocation (e.g. same physical address/same facility/same compound/same city). The one or more data centers are optionally located across different geolocations (e.g. multiple different physical addresses/multiple different facilities/multiple different compounds/multiple different cities).

[0410] The computing hardware 3671 can include a plurality of computing devices 18.1-18.N, which can implement some or all features and/or functionality of computing devices 18 described herein. The computing hardware 3671 can further include system communication resources 14, which can facilitate communication of data between computing devices 18. The system communication resources 14 can implement some or all features and/or functionality of system communication resources 14 described herein.

[0411] The energy utilization processing system 3500 and/or data processing and/or storage system 2500 of FIG. 26A can be implemented via one or more computing devices 18 of database system 10 housed in the one or more data centers. For example, execution of one or more database operations can be achieved via one more computing devices 18. As a particular example, a set of computing device nodes 37 of one or more computing devices 18, and/or a set of processing core resources 48 of one or more computing devices 18 operate in parallel to execute respective portions of a given database operation 3701. As another example, a set of disk memories 38 and/or memory drives 2425 of the computing devices 18 and/or respective nodes 37 can store data (e.g. records of one or more relational database tables), where some database operations 3701 correspond to receiving, generating, rebuilding, and/or migrating the stored data and/or where some database operations correspond to accessing the stored data (e.g. in conjunction with executing queries).

[0412] The computing hardware 3671 can alternatively or additionally include any other computing hardware (e.g. information technology (IT) hardware), for example, to implement drive resources, main memory resources, processing resources, and/or network resources of the database system 10, and/or can include any other hardware utilized to enable database system 10 to perform its respective functionality. The computing hardware 3671 can include any storage devices, servers, network equipment, server racks, routers, switches, firewalls, cables, modems, cooling systems, control systems, generators, power sources, etc. The computing hardware can optionally include any computing hardware housed in and/or implemented by a corresponding data center 3670.

[0413] Such execution of operations 3701 can rely on delivery of power 3679, supplied by one or more power supply modules 3673, to the computing devices 18, system communication resources 14, and/or other hardware of computing hardware 3671. The power supply modules 3673 can be implemented via any generators, batteries, and/or power distribution systems of database system 10. The power supply modules 3673 can be implemented via one or more power distribution units (PDUs), one or more remote power panels (RPPs), load transducers, uninterruptable power supply units (UPSs), and/or other power control systems. The power supply modules 3673 can otherwise deliver power to the various computing hardware 3671. The power supply modules 3673 can be implemented via additional computing hardware 3671 (e.g. corresponding power control systems, generators, batteries, cabling, etc.).

[0414] Some or all power 3679 can correspond to grid-based power delivered via a utility grid (e.g. electrical grid) to which the data center is connected and/or powered by. Some or all power 3679 can correspond to onsite power generated at the data center (e.g. generated via an onsite generator of the datacenter). Some or all power 3679 can correspond to battery power delivered via one or more chemical batteries and/or other batteries powering the computing hardware 3671. Some or all power 3679 can correspond to power delivered via one or more super conductors powering the computing hardware 3671. Some or all power 3679 can correspond to natural gas-based energy and/or steam-based energy. Some or all power 3679 can correspond to renewable energy (e.g. solar, wind, hydroelectric, hydrogen, ocean, geothermal, biomass, etc.). Some or all power 3679 can correspond to nuclear power generated via a nuclear power plant. Some or all power 3679 can correspond to electrical power that was generated via a power plant emitting carbon dioxide and/or other greenhouse gases.

[0415] The computing hardware 3671 can thus require being powered via power 3679 to operate and perform respective database operations 3701. Execution of various database operations 3701 by various computing devices 18 and/or other computing hardware 3671 can thus render corresponding energy utilization by database system 10. For example, the energy utilization by database system 10 when executing database operations 3701 is greater than when not executing any database operations 3701 (e.g. a given computing device 18 consumes more energy when executing an operation than when idle/unpowered). The energy utilization by database system 10 can be greater when executing a greater number of operations (e.g. in parallel or otherwise within a time frame) and/or when executing more complex/larger operations (e.g. requiring more data be read/written/communicated and/or requiring data be read/written/communicated at a higher rate) than when executing a lesser number of operations and/or less complex/smaller operations (e.g. the database system consumes more energy when more computing devices 18 are used to execute operations, and/or a given computing device 18 consumes more power when executing greater numbers/complexity of operations).

[0416] As another example, the energy utilization by database system 10 when storing data 2711 is greater than when not storing any data 2711 (e.g. a given computing device 18 consumes more energy when storing data than when idle/unpowered). The energy utilization by database system 10 can be greater when storing a greater amount of data (e.g. the database system consumes more energy when more computing devices 18 are used to store data, and/or a given computing device 18 consumes more power when storing a greater amount of data).

[0417] As used herein, energy utilization (e.g. indicated in, utilized to generate, and/or derived based on any energy utilization data 3510 described herein) can correspond to, be computed, measured, and/or estimated as, and/or be otherwise based on one or more energy utilization-based metrics such as: amount of energy (e.g. expressed in kilowatt-hours or other measure of energy) consumed via consumption of power 3679 over at least one time period; amount of power consumed from the at least one corresponding power supply (e.g. expressed in kilowatts or other measure of power), such as average power or peak power induced over the at least one time period; monetary cost (e.g. expressed in dollars or other currency, and/or expressed in carbon credits and/or carbon offsets) of power consumed over at least one time period; amount of carbon emissions (e.g. carbon dioxide released into the atmosphere, expressed by weight such as kilograms or tons of CO₂) induced over the at least one time period; amount of greenhouse gases (GHGs) (e.g. some or all warming gases released into the atmosphere, such as carbon dioxide, methane, nitrous oxide, chlorofluorocarbon CFC-11, sulpherihexafluoride, and/or other warming gases, for example, measured by weight, such as kilograms or tons of CO₂e and or expressed based on global warming potential); emissions factor, carbon intensity, conversion factor, and/or emissions intensity for activities performed by the database system, such as particular functions performed by the database system; grid utilization factor (e.g. amount/proportion of time electrical grid-based power and/or power generated onsite is used, for example, versus other power supply); performance per kilowatt-hour and/or other efficiency measure (e.g. measuring unit of activity executed by the database system performed per kilowatt hour, such as amount, speed, and/or rate of rows and/or bytes processed, read, written, stored, and/or transmitted per kilowatt-hour or other energy unit); storage capacity per kilowatt-hour (e.g. measuring unit of storage, such as amount of rows and/or bytes stored via drive resources or other memory resources per kilowatt-hour or other unit of energy); database and/or data center infrastructure efficiency (e.g. based on total energy consumption by computing devices and/or other hardware of the database system); database and/or data center performance efficiency (e.g. based on efficiency measured in kWh and/or a corresponding unit of work/power); database and/or data center power density (e.g. based on rack power consumption as a function of rack capacity); energy reuse effectiveness and/or energy reuse factor (e.g. based on reused energy of total energy); fixed to variable energy ratio (e.g. indicating how energy is effectively decreased); green energy coefficient (e.g. based on renewable energy being utilized); equipment energy efficiency (e.g. rated and/or estimated efficiency of all computing devices/memory/hardware/IT equipment of the database system and/or data center); operational energy consumption (e.g. energy consumed by all equipment/hardware, for example, if idle); power usage effectiveness (e.g. ratio of total energy consumption vs. energy consumed by all equipment/hardware); renewable energy factor (e.g. measuring renewable energy vs. total energy consumption); space, wattage, and/or performance (e.g. measuring hardware efficiency within constraints of available energy and power of corresponding data center); stranded power capacity per rack (e.g. indicating physical space available for additional equipment in the data center); technology carbon emissions (e.g. indicating total carbon emissions); peak temperature/average temperature/other metrics relating to how much/how often heat is released by respective hardware; rate/amount/cost/length of time of cooling required to cool the respective hardware (e.g. based on how much/how often heat is released); and/or any other metrics relating to energy utilization.

[0418] In some embodiments, energy utilization can be particular to different hardware components of the database system 10 that separately consume power and thus induce corresponding energy utilization. Thus, any energy utilization described herein can be divided into and/or expressed separately for different categories of such hardware. In particular, the one or more energy utilization-based metrics expressing any energy utilization described herein can be indicated for a set of energy utilization categories, which can include: drive-based energy utilization; processor-based energy utilization; memory-based energy utilization; network-based energy utilization; and/or other categories of energy utilization.

[0419] For example, in performing various database functionality, drive-based energy utilization can be induced by storage resources of the database system 10 (e.g. resources storing data 2711, such as disk memory 38, storage drives 2424, database storage 2450, external memory, solid state drives, hard disk drives, magnetic tape memory, and/or long term/persistent memory resources utilized for storage of data 2711). As another example, in performing various database functionality, processor-based energy utilization can be induced by processing resources of the database system 10 (e.g. processors on computing devices 18 and/or nodes 37, such as processing core resources 48, central processing units (CPUs), microprocessors, multi-core processors, integrated circuits, processing modules, and/or other processing resources implemented to generate and/or process data). As another example, in performing various database functionality, memory-based energy utilization can be induced by memory resources (e.g. non-drive/non-long term storage memory resources) of the database system 10 (e.g. resources used to store intermediate/temporary data/computing instructions in conjunction with performing database operations, such as main memory 40, random access memory (RAM), dynamic random access memory (DRAM), static ram (SRAM), cache memory, heap memory, huge page memory, memory modules, and/or CPU registers; for example DRAM requires refreshing via power, where use of DRAM memory for various operations can thus impact energy utilization due to power consumed for this refresh); As another example, in performing various database functionality, network-based energy utilization can be induced by network resources and/or chassis resources (e.g. system communication resources 14, inter-node communication resources, for example, implementing shuffle networks 2480 used by shuffle node sets 2485 (e.g. in performing operations such as join operations requiring communication of data between nodes), implementing transfer of data between nodes and/or storage clusters (e.g. in conjunction with migrating data 2711 between nodes/storage clusters and/or in conjunction with retrieving parity data to rebuild data structures of data 2711 from other data structures of data 2711), network hardware such as switches and routers, etc.).

[0420] In some embodiments, the energy utilization of the database system (and/or categorized utilization by different hardware types) can be particular to and/or a function of database operations being performed at a particular time, where the energy utilization is thus a function of software-based functionality of the database system, rather than simply being a function of the hardware, for example, of a corresponding one or more data centers housing the database system 10. For example, as used herein, energy utilization at a given time optionally corresponds to only a portion of total energy utilization by the one or more data centers induced by performing various database functionality (e.g. versus other energy utilization required regardless of what jobs are being performed by the database system at a given time), such as executing a particular database operation 3701 and/or storing particular data 2711.

[0421] In particular, it can be advantageous to characterize, configure, and/or reduce the energy utilization induced by performing a particular database operation 3701 (e.g. a particular task, job, sub-operation for a particular task or job, and/or other operation executed in conjunction with performing any functionality of database system 10 that thus induces power consumption to be performed). Alternatively or in addition, it can be advantageous to characterize, configure, and/or reduce the energy utilization induced by storing particular data 2711 (e.g. data under a particular schema/formatting; particular data type; particular row(s)/record(s); particular relational database table; particular dataset; particular type of compression, secondary indexing, and/or redundancy storage scheme applied; and/or other data stored in conjunction with performing any functionality of database system 10 that thus induces power consumption to be stored).

[0422] As used herein, energy efficiency (e.g. indicated in, utilized to generate, and/or derived based on any energy utilization data 3510 described herein) can denote to how favorable energy utilization is, for example, during a given period of time and/or for performing a given database functionality. For example, performing a given database operation with higher, improved, and/or otherwise more favorable energy efficiency can correspond to reducing/rendering more favorably energy utilization, for example, as defined by one or more energy utilization-based metrics (e.g. reducing overall energy consumed, reducing peak power, reducing carbon emissions, etc.). One or more energy efficiency-based metrics can be included in the one or more energy utilization-based metrics.

[0423] For example, a second strategy for performing given database functionality can be considered more energy efficient than a first strategy for performing the given database functionality based on reading, writing, receiving, generating, processing, and/or persistently storing a given amount of data under the second strategy requires less energy utilization (e.g. as defined by one or more energy utilization-based metrics) than reading, writing, receiving, generating, processing, and/or persistently storing the given amount of data under the first strategy.

[0424] As another example, a second strategy for performing given database functionality can be considered more energy efficient than a first strategy for performing the given database functionality based on reading, writing, receiving, generating, and/or processing a given amount of data under the second strategy at a given rate requires less energy utilization (e.g. as defined by one or more energy utilization-based metrics) than reading, writing, receiving, generating, and/or processing the given amount of data under the first strategy at the given rate.

[0425] As another example, a second strategy for performing given database functionality can be considered more energy efficient than a first strategy for performing the given database functionality based on performing of the given database functionality under the second strategy within a given time frame, at a given rate, at a given cost, and/or at a given reliability, requiring less energy utilization (e.g. as defined by one or more energy utilization-based metrics) than performing of the given database functionality under the second strategy within the given time frame.

[0426] As another example, a second strategy for performing given database functionality (e.g. performing one or more database operations 3701, storing given data 2711 persistently, and/or reading, writing, receiving, generating, transmitting, and/or processing given data) can be considered more energy efficient than a first strategy for performing the given database functionality when a given amount of energy utilization (e.g. as defined by one or more energy utilization-based metrics) renders the ability to read, write, receive, generate, process, and/or persistently store a greater amount of data in performing the given database functionality under the second strategy than under the first strategy.

[0427] As another example, a second strategy for performing given database functionality can be considered more energy efficient than a first strategy for performing the given database functionality when a given amount of energy utilization (e.g. as defined by one or more energy utilization-based metrics) renders the ability to read, write, receive, generate, transmit, process, and/or persistently store a given amount of data more quickly in performing the given database functionality under the second strategy than under the first strategy.

[0428] As another example, a second strategy for performing given database functionality can be considered more energy efficient than a first strategy for performing the given database functionality when a given amount of energy utilization (e.g. as defined by one or more energy utilization-based metrics) renders the ability to read, write, receive, generate, transmit, process, and/or persistently store a given amount of data more reliably in performing the given database functionality under the second strategy than under the first strategy.

[0429] As another example, a second strategy for performing given database functionality can be considered more energy efficient than a first strategy for performing the given database functionality when a given amount of energy utilization (e.g. as defined by one or more energy utilization-based metrics) renders the ability to read, write, receive, generate, transmit, process, and/or persistently store a given amount of data more cost-effectively (e.g. via more favorable energy utilization-based pricing) in performing the given database functionality under the second strategy than under the first strategy.

[0430] As another example, a second strategy for performing a given database operation 3701 can be more energy efficient than a first strategy for performing the given database operation 3701 based on the second strategy for performing the given database operation rendering lower/more favorable energy utilization (e.g. as defined by one or more energy utilization-based metrics) than the first strategy.

[0431] As another example, a second strategy for storing given data 2711 can be more energy efficient than a first strategy for storing the given data 2711 based on the second strategy for storing the given data rendering lower/more favorable energy utilization (e.g. as defined by one or more energy utilization-based metrics) than the first strategy.

[0432] As another example, second hardware can be more energy efficient than first hardware based on the second hardware being capable of reading, writing, receiving, generating, transmitting, processing, and/or persistently storing, via a given amount of energy utilization, a greater amount data, a given amount of data at a higher rate, a given amount of data more reliably, and/or a given amount of data more cost-effectively than the first hardware via the given amount of energy utilization.

[0433] As another example, second hardware can be more energy efficient than first hardware based on the second hardware being capable of reading, writing, receiving, generating, transmitting, processing, and/or persistently storing a given amount data via less energy utilization than the first hardware.

[0434] As another example, second hardware can be more energy efficient than first hardware based on the second hardware being capable of reading, writing, receiving, generating, transmitting, processing, and/or persistently storing the given amount of data within a given time frame, at a given rate, at a given cost, and/or at a given reliability than the first hardware.

[0435] As another example, a second mode of operation of the database system as a whole can be more energy efficient than a first mode of operation of the database system as a whole based on operation of the system under the second mode rendering lower/more favorable energy utilization for the database system as a whole (e.g. over a given period of time and/or in performing a given set of functionality) than the first mode.

[0436] FIG. 26C illustrates an embodiment of energy utilization processing system 3500. Some or all features and/or functionality of energy utilization processing system 3500 of FIG. 26C can implement any embodiment of energy utilization processing system 3500 and/or database system 10 described herein.

[0437] The energy utilization processing system 3500 can implement a plurality of systems that includes systems 3550-3556, operable to perform various functionality of the energy utilization processing system 3500. The various systems 3550-3556 can be implemented separately or in tandem, via shared and/or distinct computing resources (e.g. same or different computing devices 18 and/or same or different processing and/or memory resources). The various systems 3550-3556 can optionally communicate shared data with each other via storage and/or communication resources 3560.

[0438] The energy utilization processing system 3500 can implement an energy utilization measurement system 3550 operable to generate and/or process energy utilization measurement data 3570, for example, relating to characterizing of how much energy utilization was used at a given time and/or how much energy utilization was used to perform particular database functionality. The energy utilization measurement system 3550 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 27A-27L.

[0439] The energy utilization processing system 3500 can alternatively or additionally implement an energy utilization estimation system 3551 operable to generate and/or process energy utilization estimate data 3571, for example, relating to estimating of how much energy utilization will be used at a given future time and/or how much energy utilization will be used to perform particular upcoming database functionality. The energy utilization estimation system 3551 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 28A-28Q and/or 37A-37D.

[0440] The energy utilization processing system 3500 can alternatively or additionally implement an energy utilization-based operation scheduling system 3552 operable to generate and/or process energy utilization-based operation scheduling data 3572, for example, relating to scheduling of database operations at particular times, for example, to reduce peak power and/or otherwise improve energy efficiency of the database operations and/or database system as a whole. The energy utilization-based operation scheduling system 3552 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 29A-29S.

[0441] In some embodiments, some or all features and/or functionality of energy utilization-based operation scheduling system 3552 and/or some or all features and/or functionality of executing operations via scheduling of their execution described herein implements some or all features and/or functionality of query scheduling (e.g. via query scheduling module 4215, query scheduling module 2815, and/or query selection module 2950) concurrently executing queries in accordance with assigned query priority, setting/updating query priority of queries (e.g. as priority values 2942), and/or workload management as disclosed by: U.S. Utility application Ser. No. 18/482,939, entitled “PERFORMING SHUTDOWN OF A NODE IN A DATABASE SYSTEM”, filed Oct. 9, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/226,525, entitled “SWITCHING MODES OF OPERATION OF A ROW DISPERSAL OPERATION DURING QUERY EXECUTION”, filed Jul. 26, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 16/720,481, entitled “SELECTING A NORMALIZED FORM FOR CONVERSION OF A QUERY EXPRESSION”, filed Dec. 19, 2019, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0442] The energy utilization processing system 3500 can alternatively or additionally implement an energy utilization-based operation optimizing system 3553 operable to generate and/or process energy utilization-based operation optimizer data 3573, for example, relating to optimizing of database operations, for example, to improve energy efficiency of performing the database operations. The energy utilization-based operation optimizing system 3553 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 30A-33J and/or FIGS. 36A-36G.

[0443] In some embodiments, some or all features and/or functionality of energy utilization-based operation optimizing system 3553 and/or some or all features and/or functionality of executing operations via optimizing these operations (e.g. via optimizing of respective operator execution flows of operators as described herein and/or optimizing of IO pipelines described herein) implements some or all features and/or functionality of query optimization (e.g. via any embodiment of flow optimizer module 4914 and/or query processing module 2502), for example, as disclosed by: U.S. Utility application Ser. No. 18/634,450, entitled “EXECUTING MULTI-CHILD OPERATORS DURING QUERY EXECUTION VIA APPLYING A PIECEWISE SCHEDULING STRATEGY”, filed Apr. 12, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/620,268, entitled “QUERY EXECUTION VIA UPWARDS AND DOWNWARDS FLOW OF OPERATOR OUTPUT ACROSS MULTIPLE LEVELS OF A QUERY EXECUTION PLAN”, filed Mar. 28, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/226,525, entitled “SWITCHING MODES OF OPERATION OF A ROW DISPERSAL OPERATION DURING QUERY EXECUTION”, filed Jul. 26, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/309,897, entitled “OPTIMIZING AN OPERATOR FLOW FOR PERFORMING FILTERING BASED ON NEW COLUMNS VALUES VIA A DATABASE SYSTEM”, filed May 1, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/310,177, entitled “OPTIMIZING AN OPERATOR FLOW FOR PERFORMING AGGREGATION VIA A DATABASE SYSTEM”, filed May 1, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/494,230, entitled “GENERATING EXECUTION TRACKING ROWS DURING QUERY EXECUTION VIA A DATABASE SYSTEM”, filed Oct. 25, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/326,305, entitled “HANDLING NULL VALUES IN PROCESSING JOIN OPERATIONS DURING QUERY EXECUTION”, filed May 31, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0444] The energy utilization processing system 3500 can alternatively or additionally implement an energy utilization-based persistent storage configuration system 3555 operable to generate and/or process energy utilization-based persistent storage configuration data 3575, for example, relating to configuring of how data 2711 is persistently stored, such as formatting and/or schemes for if/how the data 2711 is compressed, indexed, and/or redundantly stored. The energy utilization-based persistent storage configuration system 3555 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 31A-31G.

[0445] The energy utilization processing system 3500 can alternatively or additionally implement an energy utilization-based operation limitation enforcement system 3554 operable to generate and/or process energy utilization-based operation limitation enforcement data 3574, for example, relating to allowing or disallowing operations based on whether they meet restrictions imposed by a power usage policy. The energy utilization-based operation limitation enforcement system 3554 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 34A-34I.

[0446] In some embodiments, some or all features and/or functionality of energy utilization-based operation limitation enforcement system 3554 and/or some or all features and/or functionality associated with enforcing operation requirement data and/or determining whether or not database operations are allowed as described herein implements some or all features and/or functionality of or functionality of limits imposed via service classes, imposing limitations on queries (e.g. via rulesets enforced via compliance modules), and/or imposing limits based on query attributes such as user entity, a table being accessed, and/or a query function being performed as disclosed by: U.S. Utility application Ser. No. 16/668,402, entitled “ENFORCEMENT OF SETS OF QUERY RULES FOR ACCESS TO DATA SUPPLIED BY A PLURALITY OF DATA PROVIDERS”, filed Oct. 30, 2019, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0447] The energy utilization processing system 3500 can alternatively or additionally implement an energy utilization-based operation pricing system 3556 operable to generate and/or process energy utilization-based operation pricing data 3576, for example, relating to pricing operations as a function of their energy utilization. The energy utilization-based operation pricing system 3556 can be operable to implement some or all features and/or functionality discussed in conjunction with FIGS. 35A-35G.

[0448] In some embodiments, some or all features and/or functionality of energy utilization-based operation pricing system 3556 and/or some or all features and/or functionality associated with pricing queries or other operations that have been executed already or have yet to be executed as described herein implements some or all features and/or functionality of or functionality of pricing queries and/or applying corresponding pricing schemes as disclosed by: U.S. Utility application Ser. No. 16/665,571, entitled “ENFORCEMENT OF MINIMUM QUERY COST RULES REQUIRED FOR ACCESS TO A DATABASE SYSTEM”, filed Oct. 28, 2019, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0449] Some or all systems implemented by energy utilization processing system 3500 operate based on carbon footprint related to respective energy utilization (e.g. where some or all energy utilization data 3510 is implemented as carbon footprint data relating to carbon emissions and/or other GHG emissions), for example, implementing some or all features and/or functionality discussed in conjunction with FIGS. 38A-38B.

[0450] FIG. 26D illustrates an embodiment of a database system 10 where data processing and/or storage system 2500 executes a plurality of database operations 3701.1-3701.Y (e.g. serially at different times and/or concurrently in parallel). The plurality of database operations 3701 can include same or different types of operations for same or different types of database functionality. Energy utilization data 3510 can include per-operation energy utilization data 3561.1-3561.Y, where each per-operation energy utilization data 3561 is generated for a corresponding operation, for example, to characterize energy utilization by the individual operation and/or to configure its execution (e.g. to improve energy efficiency of the operation itself and/or the database system as a whole). The energy utilization data 3510 can alternatively or additionally include aggregate operation energy utilization data 3571, for example, corresponding to an aggregation of energy utilization across execution of all of the operations 3701.1-3701.Y. Some or all features and/or functionality of database system 10 of FIG. 26D can implement any embodiment of database system 10 described herein.

[0451] FIG. 26E illustrates an embodiment of database system 10 where data processing and storage system includes a plurality of systems responsible for performing various functionality of the database system 10, for example, via a plurality of systems that includes systems 3511, 3517, 3507, 3509, and/or 2502. These various systems can be implemented separately or in tandem, via shared and/or distinct computing resources (e.g. same or different computing devices 18 and/or same or different processing and/or memory resources). The various systems 3550-3556 can optionally communicate shared data with each other via storage and/or communication resources 3560.

[0452] The plurality of systems can include a query processing system 2502, which can be operable to execute queries via execution of various query operations 2702. A given query operation 2702 can correspond to processing and execution of a corresponding query, for example, indicated in a corresponding query expression received in a query request 2914 to generate a corresponding query resultant 2920. A given query operation 2702 can optionally correspond to a portion of this processing and execution of a corresponding query, where a plurality of query operations 2702 are performed (e.g. serially at a time or concurrently in parallel) to process and/or execute a given query. A given database operation 3701 (e.g. having a query operation type) can optionally correspond to a query operation 2702, a portion of a query operation 2702, and/or multiple query operations 2702. The energy utilization data 3510 can optionally include query operation energy utilization data 3562 for such query operations 2702 (e.g. as per-operation energy utilization data 3561 for various query operations 2702), for example, to characterize energy utilization by the query operations and/or to configure their execution.

[0453] In some embodiments, some or all features and/or functionality of query processing system 2502 and/or executing of queries via execution of a query operator execution flow can include executing queries to perform types of query operations corresponding to grouped aggregation operations, join operations, and/or union distinct operations, which can be executed based on implementing via some or all features and/or functionality of grouped aggregation operations, join operations, and/or union distinct operations disclosed by: U.S. Utility application Ser. No. 18/310,177, entitled “OPTIMIZING AN OPERATOR FLOW FOR PERFORMING AGGREGATION VIA A DATABASE SYSTEM”, filed May 1, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/226,525, entitled “SWITCHING MODES OF OPERATION OF A ROW DISPERSAL OPERATION DURING QUERY EXECUTION”, filed Jul. 26, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/321,906, entitled “PROCESSING LEFT JOIN OPERATIONS VIA A DATABASE SYSTEM BASED ON FORWARDING INPUT”, filed May 23, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/494,230, entitled “GENERATING EXECUTION TRACKING ROWS DURING QUERY EXECUTION VIA A DATABASE SYSTEM”, filed Oct. 25, 2023; which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/326,305, entitled “HANDLING NULL VALUES IN PROCESSING JOIN OPERATIONS DURING QUERY EXECUTION”, filed May 31, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0454] The plurality of systems can alternatively or additionally include a data ingress system 3511, which can be operable to receive data 2511 for storage via execution of one or more ingress operations 2703. A given ingress operation 2703 can correspond to receiving, processing, and/or storing a set of data of data 2711 (e.g. prior to long term storage formatting), for example, via processing one or more incoming data streams and/or bulk data received in one or more files. A given ingress operation 2703 can optionally correspond to a portion of this receiving, processing, and/or storing of the set of data, where a plurality of ingress operations 2703 are performed (e.g. serially at a time or concurrently in parallel) to receiving, processing, and/or storing a set of data. A given database operation 3701 (e.g. having an ingress operation type) can optionally correspond to an ingress operation 2703, a portion of an ingress operation 2703, and/or multiple ingress operations 2703. The energy utilization data 3510 can optionally include ingress operation energy utilization data 3563 for such ingress operations 2703 (e.g. as per-operation energy utilization data 3561 for various ingress operations 2703), for example, to characterize energy utilization by the ingress operations and/or to configure their execution.

[0455] In some embodiments, some or all of the functionality of data ingress system 3511 and/or some or all features and/or functionality discussed in conjunction with receiving incoming rows from one or more stream sources (e.g. in row data with corresponding row numbers), processing rows for storage in pages, maintaining a durability horizon, and/or implementing one or more stream loaders (e.g. via one or more nodes) as described herein is implemented via some or all features and/or functionality regarding receiving incoming rows from one or more stream sources, processing corresponding row data such as labeled row data having corresponding row numbers, processing rows for storage in pages, maintaining a durability horizon, and/or implementing one or more stream loaders as described in U.S. Utility application Ser. No. 16/985,723, U.S. Utility application Ser. No. 16/985,957, U.S. Utility application Ser. No. 16/985,930, and/or U.S. Utility application Ser. No. 17/215,527, entitled MAINTAINING ROW DURABILITY DATA IN DATABASE SYSTEMS, filed Mar. 29, 2021, issued as U.S. Pat. No. 11,675,757 on Jun. 13, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0456] In some embodiments, some or all of the functionality of data ingress system 3511 and/or some or all features and/or functionality discussed in conjunction with loading data, for example, via one or more loading modules 2510 and/or via record processing and storage system 2505 as described herein, can implement processing of a corresponding message stream via a plurality of feed receiver modules in a fault tolerant manner as disclosed by U.S. Utility application Ser. No. 17/119,311, entitled “FAULT-TOLERANT DATA STREAM PROCESSING”, filed Dec. 11, 2020, which hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0457] The plurality of systems can alternatively or additionally include a storage-formatted data generation and/or storage system 3517, which can be operable to generate storage-formatted data from a set of data and/or store this storage-formatted data for example, long term and/or persistently (e.g. where data 2711 is formatted as storage-formatted data for persistent storage), via execution of various storage-formatted data generation and/or storage operations 2704. A given storage-formatted data generation and/or storage operation 2704 can optionally correspond to a portion of this generating and/or storing of storage-formatted data, where a plurality of storage-formatted data generation and/or storage operations 2704 are performed (e.g. serially at a time or concurrently in parallel) to generate and/or store storage-formatted data. A given database operation 3701 (e.g. having a storage-formatted data generation operation type) can optionally correspond to a storage-formatted data generation and/or storage operation 2704, a portion of a storage-formatted data generation and/or storage operation 2704, and/or multiple a storage-formatted data generation and/or storage operation 2704. The energy utilization data 3510 can optionally include storage-formatted data generation and/or storage operation energy utilization data 3564 for such storage-formatted data generation and/or storage operations 2704 (e.g. as per-operation energy utilization data 3561 for various storage-formatted data generation and/or storage operations 2704), for example, to characterize energy utilization by the storage-formatted data generation and/or storage operations and/or to configure their execution.

[0458] In some embodiments, some or all features and/or functionality of storage-formatted data generation and/or storage system 3517 and/or generating segments for storage described herein implements some or all features and/or functionality of the segment generator disclosed by: U.S. Utility application Ser. No. 16/985,723, entitled “DELAYING SEGMENT GENERATION IN DATABASE SYSTEMS”, filed Aug. 5, 2020, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes

[0459] In some embodiments, some or all features and/or functionality of data ingress system 3511 and/or storage-formatted data generation and/or storage system 3517, and/or some or all features and/or functionality of loading new data (e.g. as new pages and/or new segments), for example, via one or more loading modules 2510 and/or via record processing and storage system 2505 as described herein implements some or all features and/or functionality of loading modules, record processing and storage system, and/or any loading of data for storage and access in query execution as disclosed by: U.S. Utility application Ser. No. 18/355,497, entitled “TRANSFER OF A SET OF SEGMENTS BETWEEN STORAGE CLUSTERS OF A DATABASE SYSTEM”, filed Jul. 20, 2023; and/or U.S. Utility application Ser. No. 18/308,954, entitled “QUERY EXECUTION DURING STORAGE FORMATTING UPDATES”, filed Apr. 28, 2023; which are hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0460] In some embodiments, some or all features and/or functionality of data ingress system 3511 and/or storage-formatted data generation and/or storage system 3517, and/or some or all features and/or functionality of loading new data described herein is based on implementing some or all features and/or functionality of loading tables, for example, generated via execution of CTAS queries, as disclosed by U.S. Utility application Ser. No. 18/313,548, entitled “LOADING QUERY RESULT SETS FOR STORAGE IN DATABASE SYSTEMS”, filed May 28, 2023; which are hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0461] The plurality of systems can alternatively or additionally include a rebuilding system 3507, which can be operable to rebuild one or more data structures (e.g. where data 2711 includes one or more such data structures), via execution of various rebuilding operations 2705, for example, based on preparing for and/or responding to an outage of storage resources storing these data structures, in conjunction with ensuring persistent storage of these data structures in the case of outages. A given rebuilding operation 2705 can optionally correspond to a portion of this rebuilding of one or more data structures, where a plurality of rebuilding operations 2705 are performed (e.g. serially at a time or concurrently in parallel) to rebuild the one or more data structures. A given database operation 3701 (e.g. having a migration operation type) can optionally correspond to a rebuilding operation 2705, a portion of a rebuilding operation 2705, and/or multiple rebuilding operations 2705. The energy utilization data 3510 can optionally include rebuilding operation energy utilization data 3565 for such rebuilding operations 2705 (e.g. as per-operation energy utilization data 3561 for various rebuilding operations 2705), for example, to characterize energy utilization by the rebuilding operations and/or to configure their execution.

[0462] The plurality of systems can alternatively or additionally include a migration system 3509, which can be operable to migrate data from at least one source location to at least one destination location (e.g. where data 2711 this data for migration), via execution of various migration operations 2706, for example, in conjunction with ensuring persistent storage of data 2711, and/or based on preparing for and/or responding outages, based on responding to addition of new storage devices, and/or based on rebalancing the database system. A given migration operation 2706 can optionally correspond to a portion of this migrating of data from at least one source location to at least one destination location, where a plurality of migration operations 2506 are performed (e.g. serially at a time or concurrently in parallel) to migrate the data from the at least one source location to the at least one destination location. A given database operation 3701 (e.g. having a migration operation type) can optionally correspond to a migration operation 2706, a portion of a migration operation 2706, and/or multiple migration operations 2706. The energy utilization data 3510 can optionally include migration operation energy utilization data 3566 for such migration operations 2706 (e.g. as per-operation energy utilization data 3561 for various migration operations 2706), for example, to characterize energy utilization by the migration operations and/or to configure their execution.

[0463] In some embodiments, some or all features and/or functionality of migration system 3509 and/or execution of migration operations executes some or all features and/or functionality of segment transfers, segment transfer group process 2810 and/or transfer segment group task processing module 3510 for transferring data from storage cluster 2535.1 to 2535.2 disclosed by: U.S. Utility application Ser. No. 18/632,629, entitled “DATABASE SYSTEM PERFORMANCE OF A STORAGE REBALANCING PROCESS”, filed Apr. 11, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/355,497, entitled “TRANSFER OF A SET OF SEGMENTS BETWEEN STORAGE CLUSTERS OF A DATABASE SYSTEM”, filed Jul. 20, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0464] In some embodiments, some or all of the functionality of persistently storing data (e.g. via receiving, generating, storing, rebuilding, migrating, and/or accessing this data over time via systems of data processing and/or storage system 2500), and/or some or all of the functionality of implemented in conjunction with generating segments, storing segments (e.g. via multiple segment parts), storing segment metadata regarding segments, reloading segments, rebuilding segments, executing queries and/or performing rebuilds across multiple different storage clusters, and/or implementing a consensus protocol as described herein, is implemented based on implementing some or all features and/or functionality of the database system 10, for example, with regards to generating segments, storing segments, loading segments, rebuilding segments, and/or implementing a consensus protocol, as disclosed by: U.S. Utility application Ser. No. 18/308,954, entitled “QUERY EXECUTION DURING STORAGE FORMATTING UPDATES”, filed Apr. 28, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/310,262, entitled “GENERATING A SEGMENT REBUILD PLAN VIA A NODE OF A DATABASE SYSTEM”, filed May 1, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/355,497, entitled “TRANSFER OF A SET OF SEGMENTS BETWEEN STORAGE CLUSTERS OF A DATABASE SYSTEM”, filed Jul. 20, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0465] The plurality of systems can alternatively or additionally include an admin data logging system 3509, which can be operable to generate and/or store administrative data (e.g. debugging data, metrics tracked for observability of database system performance, other log data, and/or any metadata and/or administrative data described herein, where data 2711 optionally includes this logged admin data), via execution of various admin data logging operations 2707. For example, the administrative data can correspond to data logged in conjunction with monitoring any database operations 3701 performed by database system 10 and/or can include admin-based configuration of database operations 3701 performed by database system 10. A given admin data logging operation 2707 can optionally correspond to a portion of this logging of admin data, where a plurality of admin data logging operations 2707 are performed (e.g. serially at a time or concurrently in parallel) to log the data. A given database operation 3701 (e.g. having a migration operation type) can optionally correspond to an admin data logging operation 2707, a portion of an admin data logging operation 2707, and/or multiple admin data logging operations 2707. The energy utilization data 3510 can optionally include admin data logging operation energy utilization data 3567 for such admin data logging operations 2707 (e.g. as per-operation energy utilization data 3561 for various admin data logging operations 2707), for example, to characterize energy utilization by the migration operations and/or to configure their execution.

[0466] In some embodiments, the admin data logging operations 2707 include some or all operations performed by the energy utilization processing system 3500, where some of the log data corresponds to energy utilization data 3510 and/or data generated via processing of other energy utilization data 3510 (e.g. the log data includes various logged energy utilization measurement data 3570 and/or energy utilization estimate data 3571 as other database operations are performed over time). The database system 10 can otherwise be operable to apply energy utilization processing system 3500 to characterize and/or configure the energy utilization consumed by the energy utilization processing system 3500 in characterizing and/or configuring execution of other operations (e.g. configure how frequently energy utilization measurements are logged, how much processing be performed to schedule/optimize various operations for the purposes of energy efficiency to ensure that the energy utilization required to achieve this energy efficiency in other operations does not outweigh the benefits of the resulting scheduling and/or optimizations, etc.).

[0467] FIG. 26F illustrates an example embodiment of a data processing and/or storage system 2500. Some or all features and/or functionality of the data processing and/or storage system 2500 can implement the data processing and/or storage system 2500 of FIG. 26A and/or any embodiment of data processing and/or storage system 2500 described herein.

[0468] The data processing and storge system 2500 can include a record processing and storage system 2505 operable to implement database storage 2450 via storage of a plurality of records 2422 of one or more relational database tables 2712. For example, the record processing and storge system 2505 receives and processes incoming records for storage via database storage 2450. The record processing and storage system 2505 of FIG. 26C can implement some or all features and/or functionality of any embodiment of record processing and storage system 2505 described herein. The records 2422 of the one or more relational database tables 2712 can correspond to data 2711.

[0469] The data processing and/or storage system 2500 can include a query processing system 2502 operable to receive query requests 2914 and execute corresponding queries (e.g. via query execution module 2504) to generate corresponding query resultants via row reads performed via access to the database storage 2450 of record processing and storage system 2505. The query processing system 2502 of FIG. 26C can implement some or all features and/or functionality of any embodiment of query processing system 2502 and/or query execution module 2504 described herein.

[0470] The energy utilization processing system 3500 can communicate energy utilization data 3510 with record processing and/or storage system 2505. For example, energy utilization data 3510 includes energy utilization metrics received from and/or measured for record processing and/or storage system during execution of a database operation 3701 and/or during storage of records 2422 to indicate energy utilization induced by execution of the database operation 3701 and/or by storage of records 2422. As another example, the energy utilization data 3510 includes instructions configuring execution of one or more database operations 3701 by record processing and/or storage system 2505 (e.g. operations for receiving and/or formatting records for storage and/or maintaining storage of the records over time).

[0471] The energy utilization processing system 3500 can communicate energy utilization data 3510 with query processing system 2502. For example, energy utilization data 3510 includes energy utilization metrics received from and/or measured for query processing system during execution of a database operation 3701 (e.g. a corresponding query operation to execute a given query request) to indicate energy utilization induced by execution of the database operation 3701. As another example, the energy utilization data 3510 includes instructions configuring execution of one or more database operations 3701 (e.g. a corresponding query operation to execute a given query request) by query processing system 2502 (e.g. operations for receiving and/or formatting records for storage and/or maintaining storage of the records over time).

[0472] In some embodiments, data 2711 is stored via an object storage system and/or non-relational database-based storage system. In some embodiments, some or all features and/or functionality of generating, formatting, storing, indexing, and/or accessing data 2711 via operations 3701 described herein and/or some or all features and/or functionality of data processing and/or storage system 2500 described herein, is implemented via some or all features and/or functionality of primary storage system 2506, secondary storage system 2508, and/or object storage system 3105 disclosed by: U.S. Utility application Ser. No. 18/402,954, entitled “FILTERING RECORDS INCLUDED IN OBJECTS OF AN OBJECT STORAGE SYSTEM BASED ON APPLYING A RECORD IDENTIFICATION PIPELINE”, filed Jan. 3, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; U.S. Utility application Ser. No. 18/402,968, entitled “APPLYING FILTERING PARAMETER DATA BASED ON ACCESSING AN INDEX STRUCTURES STORED VIA OBJECTS OF AN OBJECT STORAGE SYSTEM”, filed Jan. 3, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/403,002, entitled “QUERY EXECUTION VIA COMMUNICATION WITH AN OBJECT STORAGE SYSTEM VIA AN OBJECT STORAGE COMMUNICATION PROTOCOL”, filed Jan. 3, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0473] Any embodiment of operation 3701 described herein can be implemented as part of, all of, and/or a collection of: one or more query operations 2702; one or more ingress operations 2703; one or more storage-formatted data generation and/or storage operations 2704; one or more rebuilding operations 2705; one or more migration operations 2706; and/or one or more admin data logging operations 2707. Any embodiment of operation 3701 described herein can be implemented as part of, all of, and/or a collection of any operations, operators, functions, models, algorithms, processes, and/or IO pipeline elements described herein.

[0474] In some embodiments, any embodiment of operation 3701 described herein can be implemented as training of and/or applying of one or models, such as one or more machine learning models and/or AI models, respective training functions, model execution operators, and/or other functionality of training and/or applying machine learning models via database system 10, for example, implementing some or all features and/or functionality disclosed by: U.S. Utility application Ser. No. 18/457,496, entitled “IMPLEMENTING NONLINEAR OPTIMIZATION DURING QUERY EXECUTION VIA A RELATIONAL DATABASE SYSTEM”, filed Aug. 29, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/457,568, entitled “GENERATING A DECISION TREE MODEL DURING QUERY EXECUTION VIA A RELATIONAL DATABASE SYSTEM”, filed Aug. 29, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0475] In some embodiments, any embodiment of operation 3701 described herein can be implemented as one or more window functions, one or more user-defined functions, one or more table-valued functions, and/or one or more functions implementing time series applications, for example, via implementing some or all features and/or functionality disclosed by U.S. Utility application Ser. No. 16/921,226, entitled “RECURSIVE FUNCTIONALITY IN RELATIONAL DATABASE SYSTEMS”, filed Jul. 6, 2020, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0476] FIG. 26G illustrates an example embodiment of a database system 10. Some or all features and/or functionality of the data processing and/or storage system 2500 can implement the database system of FIG. 26A and/or any embodiment of database system 10 described herein.

[0477] Data ingress system 3511 can receive records 3506 from one or more record streams and/or files. These records can be stored via a pre-storage formatting storage system 3605 before being processed for long term storage. The energy utilization by data ingress system 3511 and/or pre-storage formatting storage system 3605 to perform its respective functionality can be characterized and/or configured in corresponding energy utilization data 3510 generated and/or processed by the energy utilization processing system 3500. Some or all features and/or functionality of data ingress system 3511 of FIG. 26G can implement any embodiment of data ingress system 3511 described herein.

[0478] The records 3506 can be formatted that same as or differently from records 2422, can include some or all of the same data as records 2422, and can each correspond to a record 2422 once stored (e.g. the record 3506 is ultimately stored as a row of a relational database table). The data ingress system 3511 and/or pre-storage formatting storage system 3605 can optionally be implemented via some or all features and/or functionality of any embodiment of page generator 2511 and/or page storage system 2506, respectively, described herein.

[0479] The records 3506 can await conversion into storage-formatted data structures 3524 that include corresponding records 2422 by storage-formatted data generation and/or storage system 3517, where the resulting storage-formatted data structures 3524 are stored in one or more storage locations 3551 of database storage 2450, for example, to collectively store one or more database tables 2712. The energy utilization by storage-formatted data structures 3524 and/or database storage 2450 to perform its respective functionality can be characterized and/or configured in corresponding energy utilization data 3510 generated and/or processed by the energy utilization processing system 3500. Some or all features and/or functionality of formatted data generation and/or storage system 3517 of FIG. 26G can implement any embodiment of formatted data generation and/or storage system 3517 described herein.

[0480] The storage-formatted data structures 3524 can be implemented via some or all features and/or functionality of segments 2424 described herein. The energy utilization by storage-formatted data structures 3524 and/or database storage 2450 can be implemented via some or all features and/or functionality of segment generator 2617 and/or segment storage system 2508 described herein. The one or more storage locations 3551 can be implemented via some or all features and/or functionality of long term storage 2540 described herein. The database storage 2450 of FIG. 26G can implement any embodiment of database storage 2450 described herein.

[0481] The data ingress system 3511 and storage-formatted data generation and/or storage system 3517 can collectively implement loading of new data 2711 for storage. In some embodiments data ingress system 3511 and/or storage-formatted data generation and/or storage system 3517 can load new data 2711 for storage, for example, via performance of database operations 3701 to implement and/or perform some or all features and/or functionality any embodiments of loading modules 2510 and/or record processing and storage system 2505 described herein.

[0482] Rebuilding system 3507 can be operable to rebuild various storage formatted data structures 3524, for example, as a function of and/or based on access to other storage formatted data structures 3524 (e.g. based on their respective parity data 3527, which can implement some or all features and/or functionality of any parity data described herein), for example, in accordance with a redundancy storage scheme implemented by the storage formatted data structures 3524. The energy utilization by rebuilding system 3507 to perform its respective functionality can be characterized and/or configured in corresponding energy utilization data 3510 generated and/or processed by the energy utilization processing system 3500. Some or all features and/or functionality of rebuilding system 3507 of FIG. 26G can implement any embodiment of rebuilding system 3507 described herein.

[0483] The rebuilding system 3507 can implement some or all features and/or functionality of segment recovery module 2439 described herein, and/or via any rebuilding of segments 2424 from other segments in a same segment group described herein.

[0484] Migration system 3509 can be operable to transfer storage of various storage formatted data structures 3524 between storage locations 3551 (e.g. store in a new storage location 3551 and delete from the old storage location 3551 once storage in the new storage location is confirmed). The energy utilization by migration system 3509 to perform its respective functionality can be characterized and/or configured in corresponding energy utilization data 3510 generated and/or processed by the energy utilization processing system 3500. The migration system 3509 can optionally implement some or all functionality of rebuilding system 3507 to rebuild data structures as part of moving the data structures to the new location. Some or all features and/or functionality of migration system 3509 of FIG. 26G can implement any embodiment of migration system 3509 described herein.

[0485] In some embodiments, the migration system 3509 performs database operations 3701 to implement and/or perform some or all features and/or functionality of the segment transfer group process 2810, transfer segment group task processing module 3510, transfer segment group task processing module 3510 and/or storage rebalancing module 2905, storage rebalancing process 2915 disclosed by: U.S. Utility application Ser. No. 18/632,629, entitled “DATABASE SYSTEM PERFORMANCE OF A STORAGE REBALANCING PROCESS”, filed Apr. 11, 2024, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes; and/or U.S. Utility application Ser. No. 18/355,497, entitled “TRANSFER OF A SET OF SEGMENTS BETWEEN STORAGE CLUSTERS OF A DATABASE SYSTEM”, filed Jul. 20, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0486] Query processing system 2502 can perform queries indicated in query requests 2914 to generate corresponding query resultants 2920 via row reads to records 2422 included in storage formatted data structures 3524 via access to these data structures (and/or corresponding index data). This can include generating an operator execution flow 2517 and/or executing the operator execution flow 2517 via a plurality of nodes 37 participating in a plurality of hierarchical levels of a query execution plan 2405. The energy utilization by query processing system 2502 to perform its respective functionality can be characterized and/or configured in corresponding energy utilization data 3510 generated and/or processed by the energy utilization processing system 3500. Query processing system 2502 of FIG. 26G can implement any embodiment of query processing system 2502 and/or query execution module 2405 described herein.

[0487] FIG. 26H illustrates an embodiment of where database system 10 communicates energy utilization data 3510 with a user entity 2012, such as any user entity 2012 described herein. This can include collecting input relating to configuring of generation/collecting of energy utilization data 3510 by the database system (e.g. communication of power usage policies, communication of energy utilization thresholds/restrictions, configuration of how database operations be scheduled/optimized/restricted to reduce energy utilization, etc.) from a user entity and/or reporting energy utilization data (e.g. logged measurements/estimates/etc.) to a user entity. Options for configuration and/or reported data can be displayed to the user entity via a graphical user interface, for example, presented via a display device of a client device associated with the user entity.

[0488] FIGS. 27A-27L illustrate embodiments of a database system that implements an energy utilization measurement system 3550. Some or all features and/or functionality of the energy utilization measurement system 3550 of FIGS. 27A-27L can implement the energy utilization measurement system 3550 of FIG. 26C and/or any embodiment of the energy utilization processing system 3500 described herein. Some or all features and/or functionality of the energy utilization measurement data 3570 of FIGS. 27A-27L can implement any embodiment of energy utilization data 3510 described herein. Some or all features and/or functionality of database system 10 of FIGS. 27A-27L can implement any embodiment of database system 10 described herein.

[0489] FIG. 27A illustrates an embodiment of an energy utilization measurement system 3550 that implements a per-operation energy utilization measurement module 3631 that executes one or more energy utilization measurement functions 3649 to generate per-operation energy utilization measurement output data 3616 for a given database operation 3701.i (e.g. an operation that was already executed, or that is currently being executed) based on per-operation energy utilization measurement input data 3612 for the given database operation 3701.i. As used herein, operation 3701.i can correspond to any given operation 3701 (e.g. of the set of operations 3701.1-3701.Y executed by the database system and/or additional operations proposed but ultimately not executed by the database system, which can all optionally be individually processed as instances of operation 3701.i).

[0490] The one or more energy utilization measurement functions 3649 can be executed based on applying corresponding parameters, weights, and/or function definition(s) that are: received by energy utilization processing system 3500; accessed in memory by energy utilization processing system 3500; configured via user input by a user entity communicating with energy utilization processing system 3500; automatically generated and/or automatically updated/re-tuned over time by energy utilization processing system 3500 (e.g. via training on training data to generate a corresponding machine learning model and/or artificial intelligence (AI) model based on utilizing at least one machine learning-based training function and/or technique and/or based on utilizing at least one AI-based training function and/or technique); implemented by energy utilization processing system 3500 via artificial intelligence (e.g. based on utilizing a generative AI platform and/or other AI platform/model(s) accessible by and/or communicating with by energy utilization processing system 3500); and/or otherwise being determined by energy utilization processing system 3500. The corresponding parameters, weights, and/or function definition(s) of energy utilization measurement function(s) 3649 can be configured to generate per-operation energy utilization measurement output data 3616 as a function (e.g. deterministic function) of corresponding per-operation energy utilization measurement input data 3612.

[0491] The energy utilization measurement output data 3616 for operation 3701.i can include energy utilization measurement data 3617 for the given operation 3701.i, which can indicate one or more energy utilization values 3718 (e.g. corresponding to any of the energy utilization-based metrics described herein). Example values 3718 included in energy utilization measurement data 3617 of energy utilization measurement output data 3616 are presented in FIG. 27C.

[0492] The energy utilization measurement input data 3612 for operation 3701.i can indicate an operation type 3713 for the operation (e.g. whether the operation is a query operation 2702, ingress operation 2703, storage-formatted data generation operation 2704, rebuilding operation 2705, migration operation 2706, admin data logging operation 2707, another operation, a sub-operation of one of these operation categories, etc.). For example, the operation type 3713 indicates a value denoting an identifier for the respective operation type of operation 3701.i. The one or more energy utilization values 3718 of energy utilization estimate data 3717 can be computed by energy utilization measurement system 3550 as a function of the operation type 3713.

[0493] The energy utilization measurement input data 3612 for operation 3701.i can alternatively or additionally indicate operation parameter data 3714 further specifying factors relating to execution of the given operation, for example, that impact energy utilization in executing the operation 3701. Some or all operation parameter data 3714 can be determined prior to execution of the operation 3701, for example, as specified in configurable arguments and/or executable expression of a corresponding request to execute the operation 3701. Some or all operation parameter data 3714 optionally cannot be determined until after execution of the operation 3701 has initiated and/or completed, for example, based on state of the database system 10 when the operation 3701 is performed. Examples of operation parameter data 3714 are presented in FIG. 27D. The one or more energy utilization values 3718 of energy utilization measurement data 3617 can be computed by energy utilization measurement system 3550 as a function of the operation parameter data 3714.

[0494] The energy utilization measurement input data 3612 for operation 3701.i can alternatively or additionally indicate database condition data 3715 during execution of operation 3701.i further specifying factors relating to the state of database system 10 at the time the operation was executed, for example, that impact energy utilization in executing the operation 3701. This can include current information such as: database system wide energy utilization (e.g. corresponding values for any metrics described herein), type of power (e.g. battery vs. grid-based vs. renewable) being used by the database at the time the operation was executed; a current mode of operation of storage of the database in persistently storing data 2711 at the time the operation was executed; an emissions factor for the database's current mode of operation/functionality at the time the operation was executed; current pricing scheme at the time the operation was executed; configuration of the database system 10 at the time the operation was executed; how much data 2711 is stored across how many tables across how many devices at the time the operation was executed; which nodes/devices are online vs offline/active vs. idle at the time the operation was executed; other operations concurrently executing when the operation 3701.i was executed; various system metadata/state data mediated via one or more storage clusters, such as any state data described herein, etc. The one or more energy utilization values 3718 of energy utilization measurement data 3617 can be computed by energy utilization measurement system 3550 as a function of the database condition data 3715.

[0495] The energy utilization measurement input data 3612 for operation 3701.i can alternatively or additionally include power meter measurement data 3619 measured (e.g. by power monitoring hardware of the database system 10) during execution of operation 3701.i, for example, while any number of database operations 3701 and/or other activities contributing to energy consumption may have also been performed by database system 10. The one or more energy utilization values 3718 of energy utilization measurement data 3617 can be computed by energy utilization measurement system 3550 as a function of the power meter measurement data 3619.

[0496] The values 3718 of energy utilization measurement data can correspond to singular values for energy utilization (e.g. for of the energy utilization-based metrics), for example, based on the measurement taken via energy utilization measurement function being known/expected to be accurate and/or a singular estimated value being sufficient (e.g. a mean/center of a corresponding distribution, given the input data 3612). These can alternatively or additionally correspond to value ranges (e.g. bounded range by min and max value, confidence intervals, range having a center and span dictated by the input data 3612, for example, based on how confident the estimate for measurement is based on the input data 2712, etc.) for energy utilization (e.g. for of the energy utilization-based metrics), for example, based on guaranteeing/expecting the actual value to fall within the presented range and/or based on the measurement taken via energy utilization measurement function being an estimate rather than a value guaranteed to be accurate. These can alternatively or additionally correspond to probability distribution data (e.g. expected value and/or standard deviation for the measurement value given the input data 3612, a probability mass function (PMF) and/or probability density function (PDF) for the measurement value, given the input data 3612, and/or other distribution data).

[0497] In some embodiments, the energy utilization measurement data 3617 can characterize an amount/portion of energy utilization by the database system 10 attributed to execution of the particular database operation 3701.i. For example, if energy utilization measured by some or all of the database system as a whole was measured as a value X (e.g. for one or more energy utilization metrics) across a temporal period in which database operation 3701.i was executed, and if value Y is value 3718 determined to be energy utilization consumed by the database operation, a value Z=X−Y is thus the energy utilization that would have been expected to have been consumed over the temporal period if the database operation had not been executed. While X can be directly measurable (e.g. based on power meters or other power consumption monitoring of the database system 10 as a whole, or one or more particular discrete portion of database system 10), the value Y may correspond to an estimate for how much of the energy utilization X is attributed to the database operation 3701.i, even in the case where database operation 3701.i was already executed.

[0498] FIG. 27B illustrates an example of how energy utilization by database system 10 over a period of time is rendered via energy utilization induced via various operations 3701 during this period of time. In particular, during a particular time period 3632, database system energy utilization 3401 (e.g. power consumption over the temporal period 3632 as plotted in FIG. 27B) can be induced by energy utilization 3402 of each of a plurality of operations executing during this temporal period 3632 (e.g. where some of all of these operations execute concurrently for some or all portions of the time period).

[0499] For example, a spike in power of database system energy utilization 3401 near the end of temporal period 3632 can be based on higher power consumption of energy utilization 3402.1 and 3402.i induced by executing operations 3701.1 and 3701.i at this time, respectfully. For example, the power consumed at a particular time is a summation of power consumed to execute all operations at that particular time (e.g. as well as additional power consumed for other functionality of database system 10 requiring power at the particular time).

[0500] Furthermore, corresponding energy utilization 3402.i of a given operation 3701.i can be induced by energy utilization 3403 by each of a plurality of resources having corresponding/different resource types 3404. For example, a spike in power of operation energy utilization 3402.i near the end of temporal period 3632 can be based on a large spike in power consumed by operation 3701.i via resource type 3404.j at this time, and/or a smaller prior spike at a previous time can be induced based on a small spike in power consumed by operation consumed by operation 3701.i via resource type 3404.1 at this previous time. The resource based-energy utilization 3403 can each correspond to energy utilization of a given device (e.g. given computing device 18), and/or across a plurality of devices of a particular type (e.g. resource based-energy utilization 3403.i.1 corresponds to drive-based energy utilization for resource type 3404.1 corresponding to a drive-based resource type; resource based-energy utilization 3403.i.2 corresponds to processor-based energy utilization for resource type 3404.2 corresponding to a processor-based resource type; resource based-energy utilization 3403.i.3 corresponds to memory-based energy utilization for resource type 3404.3 corresponding to a memory-based resource type; and/or resource based-energy utilization 3403.i.4 corresponds to network-based energy utilization for resource type 3404.4 corresponding to a network-based resource type).

[0501] FIG. 27C illustrates an example of energy utilization measurement data 3617 of energy utilization measurement output data 3616 for operation 3701.i generated by energy utilization measurement system 3550. The energy utilization measurement data 3617 can include total energy measurement data 3680, peak power measurement data 3681, temporal energy utilization distribution measurement data 3682, and/or resource type-based energy utilization measurement data 3683.

[0502] The total energy measurement data 3680 can characterize how much energy, and/or associated monetary cost, was required to execute the database operation 3701.i over the duration of the database operation (e.g. as a portion of all energy consumed by the database system during the temporal period in which the database operation is executed). The total energy measurement data 3680 can indicate a measured value for total energy utilization measurement amount 3684 (e.g. a singular value) corresponding to a value indicating total amount of energy utilized (e.g. expressed in kilowatt-hours, measure of energy, integral and/or summation of power utilization by the database operation over a corresponding temporal period in which the database operation was executed, and/or as a value for any of the energy utilization-based metrics described herein). The total energy measurement data 3680 can alternatively or additionally include a measured value for total energy utilization cost 3685, which can indicate a total energy utilization cost (e.g. a singular value, for example, corresponding to price/monetary/carbon credit/carbon offset) corresponding to a value indicating cost/price of the total amount of energy utilized. The total energy measurement data 3680 can alternatively or additionally include a measured value range for energy utilization amount and/or cost 3686 corresponding to a range (e.g. bounded by max and min values, a confidence interval, etc.) of value that the actual value for total energy utilization amount and/or total energy utilization cost is known/expected to fall within. The total energy measurement data 3680 can alternatively or additionally include probability distribution data (e.g. expected value and/or standard deviation, parameters defining a PDF or PMF for the corresponding distribution curve, etc.) for measured total energy utilization amount and/or cost 3687.

[0503] The peak power measurement data 3681 can characterize a maximum amount of power, and/or associated monetary cost, that was required to execute the database operation 3701.i at any given time during the temporal period in which the database operation was executed. In some cases, peak power of the database system as a whole occurred at this time (e.g. the spike in power required at the given time to execute database operation 3701.i was substantial enough to render corresponding peak power across the database system during the temporal period in which the database operation was executed, and/or across a longer period of time, for example, due to being more significant than other concurrent activities by the database system over the temporal period and/or more significant than additional activities over the longer period of time). In other cases, peak power of the database system occurred at a different time (e.g. the peak power for the operation was not substantial enough to render peak power by the database system as a whole at that time, for example, due to other concurrently executed database operations with their own spikes in power also having been executing at different times, having been load balanced such that various peak powers of various database operations did not compound, another database operation having a larger peak power during a different time in the temporal period, etc.).

[0504] The peak power measurement data 3681 can include a measured value for peak power amount 3688 (e.g. a singular value, expressed in kilowatts, corresponding to a maximum power induced by the database operation 3701.i over a temporal period in which the database operation was executed, optionally expressed in kilowatt-hours or other energy measure for a small time window (e.g. a second or fraction of a second) within the temporal period the database operation was executed having highest energy consumption over all time windows within the temporal period, and/or as a value for any of the energy utilization-based metrics described herein). The peak power measurement data 3681 can include a measured value for peak power cost 3689, which can indicate cost attributed to the peak power amount (e.g. a singular value, for example, corresponding to price/monetary/carbon credit/carbon offset). The total energy measurement data 3671 can alternatively or additionally include a measured value range for peak power amount and/or cost 3690 corresponding to a range (e.g. bounded by max and min values, a confidence interval, etc.) of value that the actual value for peak power amount and/or peak power cost is known/expected to fall within. The total energy measurement data 3681 can alternatively or additionally include probability distribution data (e.g. expected value and/or standard deviation, parameters defining a PDF or PMF for the corresponding distribution curve, etc.) for measured total peak power amount and/or cost 3691.

[0505] The temporal energy utilization distribution measurement data 3682 can characterize power consumption by the database operation over time, for example, based on a measured execution duration of time indicating how long the execution of database operation 3701.i lasted (e.g. length of the corresponding temporal period in which the database operation 3701.i was executed). This can characterize when power spiked/dipped during execution of the database operation, for example, based on some portions of the database operation's execution requiring more power than others.

[0506] The temporal energy utilization distribution measurement data 3682 can include measured absolute peak power timing data 3692 indicating when the peak power of the database operation occurred, for example, in a standardized time measure across the database system 10 (e.g. a time in coordinated universal time (UTC) time; occurred in the daytime vs. in the nighttime; occurred over the weekend vs. during a weekday, etc. (e.g. expressed as a singular time value, time range, and/or probability distribution value for the absolute time). The temporal energy utilization distribution measurement data 3682 can alternatively or additionally include measured relative peak power timing data 3693 indicating when the peak power occurred relative to the temporal period in which the database operation was executed (e.g. after 3 seconds of execution; when the operation was 20% complete; after 15% of the total duration of the database operation execution elapsed, etc.; expressed as a singular time value, time range, and/or probability distribution value for the absolute time). The temporal energy utilization distribution measurement data 3682 can alternatively or additionally include indicating distribution of power consumption over the execution duration 3694 (e.g. power utilization attributed to the database operation execution across a plurality of instantaneous points in time during the temporal period, energy utilization across a plurality of clock cycles/short time windows within the temporal period, a function definition defining a corresponding curve for power consumption as a function of time, etc.), and/or can otherwise indicate times that other spikes in power consumption induced by the database operation occurred (e.g. over a predetermined threshold amount), times that dips in power occurred (e.g. under a predetermined threshold amount), etc. (e.g. expressed as a singular time values, time ranges, and/or probability distribution value for the absolute times, mapped to corresponding power levels).

[0507] The resource-based energy utilization measurement data 3683 can characterize how energy utilization by the database operation's execution is dispersed across different resources of the database system. This can be useful in identifying which resources experience the greatest power draw, power spikes, and/or highest contribution to energy utilization cost in executing the corresponding database operation.

[0508] The resource-based energy utilization measurement data 3683 can include drive-based energy utilization measurement data 3695 indicating drive-based energy utilization induced via execution of the database operation, such as energy utilization by storage devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve storing and/or accessing data (e.g. via IO operators and/or execution of an IO pipeline) in these storage devices and/or correspond to operations involving persistent storage of data. The drive-based energy utilization measurement data 3695 can include energy utilization measurement data 3680, peak power measurement data 3681, and/or temporal energy utilization distribution measurement data 3682 attributed specifically to drive-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to drive-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to drive-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to drive-based resources; etc.). The drive-based energy utilization measurement data 3695 can optionally further indicate distribution of such drive-based energy consumption across different types of storage devices.

[0509] The resource-based energy utilization measurement data 3683 can include processor-based energy utilization measurement data 3696 indicating processor-based energy utilization induced via execution of the database operation, such as energy utilization by processor devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve processing data via these processing devices. The processor-based energy utilization measurement data 3696 can include energy utilization measurement data 3680, peak power measurement data 3681, and/or temporal energy utilization distribution measurement data 3682 attributed specifically to processor-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to processor-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to processor-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to processor-based resources; etc.). The processor-based energy utilization measurement data 3696 can optionally further indicate distribution of such processor-based energy consumption across different types of processors (e.g. different types of processing devices, different types of processing cores within multi-core processing devices etc.).

[0510] The resource-based energy utilization measurement data 3683 can include memory-based energy utilization measurement data 3697 indicating memory-based (e.g. for non-storage-based memory) energy utilization induced via execution of the database operation, such as energy utilization by memory devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve storing intermediate data (e.g. hash maps, pages of rows, etc.) generated in executing the database operation via these memory devices. The memory-based energy utilization measurement data 3697 can include energy utilization measurement data 3680, peak power measurement data 3681, and/or temporal energy utilization distribution measurement data 3682 attributed specifically to memory-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to memory-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to memory-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to memory-based resources; etc.). The memory-based energy utilization measurement data 3697 can optionally further indicate distribution of such memory-based energy consumption across different types of memory (e.g. RAM vs. cache memory, etc.).

[0511] The resource-based energy utilization measurement data 3683 can include chassis and/or network-based energy utilization measurement data 3698 indicating network-based/chassis-based energy utilization induced via execution of the database operation, such as energy utilization by network devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve communicating data between devices (e.g. between nodes 37 at same or different levels of a query execution plan, etc.) and/or involve accessing external networks (e.g. the internet), in executing the database operation via these network devices. The network-based energy utilization measurement data 3698 can include energy utilization measurement data 3680, peak power measurement data 3681, and/or temporal energy utilization distribution measurement data 3682 attributed specifically to network-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to network-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to network-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to network-based resources; etc.). The network-based energy utilization measurement data 3698 can optionally further indicate distribution of such network-based energy consumption across different types of network devices.

[0512] FIG. 27D illustrates example parameters of operation parameter data 3614 of energy utilization measurement input data 3612 for operation 3701.i, for example, generated by energy utilization measurement system 3550 or otherwise determined as parameters characterizing the operation 3701.i for which energy utilization measurement data (and/or other output by energy utilization processing system 3500) is to be generated.

[0513] In particular, parameters specific to the given operation 3701.i can impact the energy utilization induced in executing the corresponding operation. Thus, different operations 3701.i, and/or even different instances of the same operation having some or all different parameters of their respective operation parameter data 3714, can have different respective per-operation energy utilization (e.g. measured and/or estimated by the energy utilization processing system 3500) induced by differences in their respective operation parameter data 3714.

[0514] Some or all operation parameters of operation parameter data 3614 can be determined/determinable prior to execution of the operation 3701.i, for example, as defined in an instruction/expression defining the operation 3701.i Other operation parameter data 3614 optionally cannot be determined until the execution of operation 3701.i has begun/completed, for example, based on being based on the state of the database system 10. Some or all operation parameters of operation parameter data 3614 can be automatically measured/estimated by the energy utilization processing system 3500 for the corresponding operation based on the expression/instructions for the given operation (e.g. prior to execution), based on the state of the database system 10 (e.g. prior to, during, and/or after execution), and/or based on measurements/monitoring during the execution of the of the operation.

[0515] In some embodiments, some or all operation parameters of operation parameter data 3614 are fixed, for example, based on constraints/requirements for executing the corresponding operation 3701.i. In some embodiments, some or all operation parameters of operation parameter data 3614 are automatically selected/configured by the energy utilization processing system 3500 for the operation 3701.i prior to being performed, for example, to improve energy utilization for the operation 3701.i and/or for the database system as a whole (e.g. in scheduling and/or optimizing the corresponding operation as discussed in further detail herein).

[0516] Some or all features of operation parameter data 3614 of FIG. 27D can implement any embodiment operation parameter data 3714 described herein, including operation parameter data 3714 used as input for other functions of other systems of energy utilization processing system 3500 described herein, where any of the other outputs (e.g. scheduling data, optimization data, restriction data, etc.) generated by any system of energy utilization processing system can be generated as a function of one or more parameters of operation parameter data 3614 of FIG. 27D.

[0517] The operation parameter data 3614 can include (and/or can be defined based on) an expression (and/or one or more function calls with corresponding configured arguments) to be executed 3602. For example, the expression/function call/corresponding arguments is defined/indicated in a corresponding request (e.g. generated by/received from a user entity such as a person or automated system) to execute the operation and/or otherwise defines the operation to be executed.

[0518] The operation parameter data 3614 can include operation priority data 3814, which can indicate a priority value for the operation 3701.i (e.g. relative to other operations). This can be based on an urgency of executing the corresponding operation (e.g. a query related to an amber alert is more time-critical than an administrative function to log activity) and/or a priority of a corresponding user. The operation priority data 3814 can be configured in conjunction with workload management. The operation priority data 3814 can be indicated in a request for execution of the corresponding operation 3701.i. The operation priority data 3814 can be generated/updated/configured via implementing some or all features and/or functionality query scheduling and/or WLM described herein, for example, to schedule queries in accordance with query priority. For example, operation priority data 3814 can be relevant in constricting when/how soon/how quickly the operation is executed, which can impact energy utilization (e.g. operations executed more quickly can induce higher/less favorable energy utilization; operations executed sooner can constrain scheduling strategies used to reduce peak power, etc.).

[0519] The operation parameter data 3614 can alternatively or additionally include a requesting user entity 2012 (e.g. via a corresponding identifier value identifying the user entity 2012). For example, requesting user entity 2012 can be relevant in constricting how the corresponding operation is prioritized, scheduled, and/or configured for execution, which can impact energy utilization.

[0520] The operation parameter data 3614 can alternatively or additionally indicate an amount of data (e.g. number of rows and/or bytes) read 3622 in executing the corresponding operation 3701.i. This can correspond to a known and/or estimated amount of data to be read, determined prior to execution of the corresponding operation 3701.i. This can correspond to a known and/or estimated amount of data that was determined to be read after execution of the corresponding operation 3701.i. The amount of data read 3622 can correspond to data read from particular memory, such as disk memory/storage resources (e.g. rows read from relational database tables in database storage, for example, via execution of IO operators). The amount of data read 3622 can correspond to data read from other memory, such as RAM and/or cache memory (e.g. reading from a hash map or other structure maintained in memory only for the life of the corresponding operation). For example, amount of data read 3622 can be relevant as higher amounts of data read 3622 can contribute to higher/less efficient memory utilization.

[0521] The operation parameter data 3614 can alternatively or additionally indicate an amount of data (e.g. number of rows and/or bytes) written 3623 in executing the corresponding operation 3701.i. This can correspond to a known and/or estimated amount of data to be written, determined prior to execution of the corresponding operation 3701.i. This can correspond to a known and/or estimated amount of data that was determined to be written after execution of the corresponding operation 3701.i. The amount of data written 3623 can correspond to data written to particular memory, such as disk memory/storage resources (e.g. new rows written added relational database tables in database storage). The amount of data written 3623 can correspond to data written to other memory, such as RAM and/or cache memory (e.g. writing a hash map or other structure written to memory only for the life of the corresponding operation). For example, amount of data written 3623 can be relevant as higher amounts of data written 3623 can contribute to higher/less efficient memory utilization.

[0522] The amount of data written 3623 can optionally correspond to (and/or operation parameter data 3614 can otherwise indicate) size of data blocks written (e.g. even if a total amount of data being written is fixed, amount of data written can relate to how many blocks the data is written to and/or size of each data block). For example, write operations that are consolidated (e.g. via queueing data to be written until a threshold amount of data is reached) to write to larger chunks (e.g. larger than 4 k blocks) can render lower energy utilization and/or data of a given write operation chunked into a smaller number of large chunks (e.g. larger than 4 k blocks) can render lower energy utilization.

[0523] In some embodiments, the amount of data written can be processed differently in estimating energy utilization than the amount of data read. For example, writing a given amount of data can be known/estimated induce greater energy utilization than reading this amount of data.

[0524] The operation parameter data 3614 can alternatively or additionally indicate a level of parallelization 3624 (e.g. how many parallelized nodes/processing core resources/threads are executing in parallel, concurrently; how many nodes participate in a given shuffle node set; etc.). For example, level of parallelization 3624 can be relevant as higher amounts of level of parallelization 3624 can contribute to higher/less efficient energy utilization (e.g. greater power consumption at the given time that parallelized resources process a plurality of data in parallel vs. if this data was processed serially, which can contribute to peak power).

[0525] The operation parameter data 3614 can alternatively or additionally indicate row cardinality data 3838. For example, the row cardinality data 3838 indicates row cardinality of data to be accessed (e.g. in a query, for example, where this data is filtered and/or processed to generate a query resultant) and/or stored (e.g. as segments or other storage formatted data structure). The row cardinality 3614 can impact how efficiently the operation can be executed, for example, by impacting how much data is processed (e.g. size/memory consumed by a hash map being built during the execution; amount of data processed during IO/filtering of a corresponding query; etc.). For example, higher row cardinality indicated by row cardinality data 3838 can be relevant as it can induce higher levels of processing which can contribute to higher/less efficient memory utilization. In some embodiments, the row cardinality data can be related to efficiency of grouping rows by cluster key, relevant to IO efficiency in generating segments and/or accessing/filtering rows of these segments.

[0526] The operation parameter data 3614 can alternatively or additionally indicate IO efficiency metrics 3839 (e.g. such as a ratio of data emitted vs data processed). For example, higher/more favorable IO efficiency indicated by IO efficiency metrics 3839 can be relevant as it can induce lower levels of processing which can contribute to lower/more efficient memory utilization. The IO efficiency metrics can be implemented as any embodiment of secondary indexing efficiency metrics and/or any means of evaluating IO efficiency described herein.

[0527] The operation parameter data 3614 can alternatively or additionally indicate start and/or end time of execution 3625 and/or execution duration of time 3637. For example, higher duration of execution can contribute to higher/less favorable memory utilization, or optionally lower/more efficient memory utilization in the case where peak power is reduced via longer overall execution. The actual start and end times (e.g. relative to times that other operations/functionality of the database system was performed) can be relevant in impacting peak power by the database system (e.g. based on whether many operations are executed simultaneously, which can induce higher peak power by the database system than the case where execution of these operations is spread out over time).

[0528] The operation parameter data 3614 can alternatively or additionally indicate one or more relational database tables and/or columns involved 3633, for example, indicating how many tables and/or columns are involved, their corresponding sizes, corresponding types of data (E.g, integer vs. string vs. float etc.) stored in the tables/columns, corresponding table names/identifiers and/or corresponding column names/identifiers (e.g. mapped to additional information regarding these tables/columns that is considered part of the operation parameter data). For example, a greater numbers of tables and/or greater numbers of rows across these tables (e.g. to be written to storage and/or accessed in storage) can be relevant as it can induce higher levels of processing which can contribute to higher/less efficient memory utilization. As another example, a greater numbers of columns and/or columns having larger data types (e.g. floats vs Boolean values) can be relevant as it can induce higher levels of processing which can contribute to higher/less efficient memory utilization.

[0529] The operation parameter data 3614 can alternatively or additionally indicate one or more storage clusters and/or computing clusters (e.g. vm clusters involved) 3634, for example, indicating how many clusters are involved, their corresponding sizes, and/or corresponding cluster identifiers (e.g. mapped to additional information regarding these clusters that is considered part of the operation parameter data). For example, each storage/computing cluster can include a set of nodes 37. For example, a greater number of clusters and/or greater number of nodes across these clusters (e.g. to store new data, to access their data, and/or to process data, for example, as part of a query execution plan or loading operation) can be relevant as it can induce higher levels of processing which can contribute to higher/less efficient memory utilization.

[0530] The operation parameter data 3614 can indicate data structuring parameters 3639 of data read and/or written in executing the operation 3701.i. For example, the data structuring parameters 3639 can impact: energy utilization required to generate storage formatted data structures for storage; energy utilization required to maintain storage of storage formatted data structures; energy utilization required to guarantee persistent storage of storage formatted data structures (e.g. to migrate/rebuild the storage formatted data structures over time for example, in anticipating/responding to outages and/or rebalancing the system); and/or energy utilization required to access the underlying data stored via the storage formatted data structures.

[0531] The data structuring parameters 3639 can indicate a compression scheme (e.g. corresponding compression ratio) of data generated/stored/accessed 3635. For example, greater compression ratio/greater levels of compression (e.g. less storage memory resources utilized to store particular underlying data via higher levels of compression) can be relevant as it can induce: higher/less efficient energy utilization required to compress the underlying data to generate storage formatted data structures for storage; lower/more efficient energy utilization required to maintain storage of storage formatted data structures; and/or higher/less efficient energy utilization required to decompress the storage formatted data structures to access the underlying data stored via the storage formatted data structures.

[0532] The data structuring parameters 3639 can alternatively or additionally indicate a secondary indexing scheme for data generated/stored/accessed 3636, for example, implementing any type of secondary indexing structure and/or respective secondary indexing scheme described herein. For example, higher levels of indexing (e.g. more index structures, more columns indexed, more complicated/larger index structures) can be relevant as it can induce: higher/less efficient energy utilization required to generate the index structures for storage; higher/less efficient energy utilization required to maintain storage of the index structures; and/or lower/more efficient energy utilization required to access/filter rows of the table that is indexed (e.g. in applying filtering parameters of a corresponding query).

[0533] The data structuring parameters 3639 can alternatively or additionally indicate a redundancy storage scheme for data generated/stored/accessed 3640. For example, higher levels of redundancy and/or anticipation of higher failure rates (e.g. more parity data, more duplicated data, more segments in a same segment group) can be relevant as it can induce: higher/less efficient energy utilization required to generate the index structures for storage; and/or higher/less efficient energy utilization required to guarantee persistent storage of the index structures (e.g. these higher levels of energy utilization may be required as a function of higher failure rates by the database system and/or higher probability of data not being lost being required).

[0534] The data structuring parameters 3639 can alternatively or additionally indicate targets/restrictions for size/number of rows/pages included in corresponding data structures 3101 (e.g. dictating segment size and/or size of conversion page sets). For example, larger segments and/or larger conversion page sets induce greater energy consumption (e.g. to group rows by cluster key and/or generate respective segments), despite rendering more favorable clustering by cluster key and/or other benefits.

[0535] The operation parameter data 3614 can alternatively or additionally indicate resource usage data 3627. For example, the resource usage data 3614 can be relevant at it can impact total energy utilization via execution of the operation 3701.i and/or energy utilization by different resources in executing the operation 3701.i.

[0536] The resource usage data 3614 can include number/types/location/identifiers of nodes and/or devices involved 3628 in executing the operation 3701.i. For example, higher amounts of nodes/devices and/or less energy efficient types of nodes/devices can be relevant as it can induce higher/less efficient energy utilization.

[0537] The resource usage data 3614 can alternatively or additionally indicate drive usage and/or access amount, type and/or time 3629 in executing the operation 3701.i. For example, higher amounts of drive usage, higher amounts of drive access, and/or greater amounts of time accessing/using drives can induce higher energy utilization (e.g. higher drive-based energy utilization via drive-based resources).

[0538] The resource usage data 3614 can alternatively or additionally indicate processor usage and/or access amount, type and/or time 3630 in executing the operation 3701.i. For example, higher amounts of processor usage and/or greater amounts of time using processors can induce higher energy utilization (e.g. higher processor-based energy utilization via processor-based resources).

[0539] The resource usage data 3614 can alternatively or additionally indicate memory usage and/or access amount, type and/or time 3631 in executing the operation 3701.i. For example, higher amounts of memory (e.g. non-drive; RAM and/or cache) usage, higher amounts of memory (e.g. non-drive; RAM and/or cache) access, and/or greater amounts of time accessing/using memory (e.g. non-drive; RAM and/or cache) can induce higher energy utilization (e.g. higher memory-based energy utilization via memory-based (e.g. non drive-based) resources).

[0540] The resource usage data 3614 can alternatively or additionally indicate chassis and/or network usage and/or access amount, type and/or time 3632 in executing the operation 3701.i. For example, higher amounts of network usage and/or greater amounts of time using network resources can induce higher energy utilization (e.g. higher processor-based energy utilization via network-based resources).

[0541] The resource usage data 3614 can alternatively or additionally indicate power source usage and/or access amount, type and/or time 3643 in executing the operation 3701.i. For example, different types of power sources (e.g. grid-based power vs. onsite generated power vs. battery-based power vs. super conductor-based power vs. renewable energy, etc.) induce different levels of energy utilization (e.g. particular as related to carbon footprint and/or cost of powering devices via respective different types of power).

[0542] The operation parameter data 3614 can alternatively or additionally indicate sub-operation data 3638. For example, the sub-operation data 3638 can be relevant as execution of various different sub-operations of the operation 3701.i it can influence energy utilization by the database operation 3701.i.

[0543] The sub-operation data 3638 can indicate a sub-operation set 3639 of sub-operations 3701.i.1-3701.i.Z of the operation 3701.i, for example, corresponding to different portions/steps of the operation (e.g. performed serially or in parallel). The sub-operation data 3638 can alternatively or additionally indicate a serialized/parallelized flow 3626 of the sub-operations 3701.i.1-3701.i.Z (e.g. an ordering the sub-operations be performed, parallelized performance of sub-operations, how output of one sub-operation is processed as input of another, etc.).

[0544] The sub-operation data 3626 can alternatively or additionally indicate sub-operation parameter data 3714.i.1-3714.i.Z for the sub-operations 3701.i.1-3701.i.Z, where each given sub-operation can have its own operation parameter data 3714 (e.g. values for some or all of the parameters of operation parameter data 3714 and/or otherwise described herein, specific to the given sub-operation). The energy utilization for the operation 3701.i can optionally be determined as an aggregation of/some function of the energy utilization of its individual sub-operations, for example, as discussed in conjunction with FIG. 27G.

[0545] As a particular example, the operation 3701.i is a query operation corresponding to a query expression that is executed via an operator execution flow 2517 (e.g. indicated by flow 3626), where sub-operations 3701.i.1-3701.i.Z each correspond to one or more sub-flow of the operator execution flow 2517 (e.g. executed at different levels of the query execution plan) and/or each correspond to operations 2520 of the operator execution flow 2517. As another example, the operation 3701.i includes a plurality of parallelized instances of a given process, where multiple ones of the sub-operations 3701.i.1-3701.i.Z correspond to different ones of the plurality of parallelized instances. As another example, the operation 3701.i includes a process performed on different data portions (e.g. different rows, different tables, different segments/storage formatted data structures) of data 2711, where performance of the process upon a given data portion corresponds to one sub-operations. As another example, any operation/function/process/functionality/step performed by database system described herein can be considered an operation 3701, and/or a sub-operation as part of a larger operation 3701.

[0546] FIG. 27E-27F illustrate embodiments of how energy utilization measurement data 3617 generated by energy utilization measurement system 3550 can be processed/communicated.

[0547] As illustrated in FIG. 27E, the energy utilization measurement data 3617 generated for a given operation 3701.i can be communicated to a user entity (e.g. as part of log data or other aggregate data for some or all operations performed over a temporal period, such as a given hour, day, week, month or year). For example, the energy utilization measurement data is displayed via a display device (e.g. as part of a plot/table of energy utilization measurement data for multiple operation performed over the temporal period).

[0548] As illustrated in FIG. 27F, the energy utilization measurement data 3617 generated for a given operation 3701.i can be sent to/stored in memory accessible by other systems of the energy utilization processing system 3500. For example, energy utilization measurement data 3617 generated for a given operation 3701.i (and/or for a plurality of operations performed over a temporal period) can be processed by energy utilization estimation system 3551, for example, to train a model/configure a function utilized to generate estimates for subsequent operations (e.g. as historical energy utilization measurement data). As another example, energy utilization measurement data 3617 generated for a given operation 3701.i can be processed by energy utilization-based operation pricing system 3556, for example, to dictate how much execution of the corresponding database operation costs (e.g. how much a user entity requesting the operation be performed is charged, for example, in monetary currency, carbon offsets, etc.).

[0549] While not illustrated, the energy utilization measurement data 3617 generated for various operations 3701 can be stored in storage resources of database system 10. For example, one or more dedicated relational database tables (e.g. metadata/admin/persistent system tables) store the energy utilization measurement data 3617 for each of a plurality of operations 3701, for example, where each row of the table corresponds to one operation 3701 and stores the energy utilization measurement data 3617 for the operation (e.g. in one or more respective columns, for example, each storing the measured value for a corresponding metric).

[0550] FIG. 27G illustrates an embodiment of energy utilization measurement system 3550 that generates energy utilization measurement output data 3616 for a given operation 3701.i as a function of its sub-operations.

[0551] In some embodiments, a sub-operation identification module 3769 can determine per-operation energy utilization input data 3612 for each of a plurality of identified sub-operations 3701.i.1-3701.i.Z (e.g. identified from sub-operation data 3638 of the operation 3701.i, where the per-operation energy utilization input data 3612 for each given sub-operation is optionally based on sub-operation parameter data 3714 for each given sub-operation. The energy utilization measurement function(s) 3649 can be performed to process the per-operation energy utilization measurement input data 3612 for each sub-operation (individually/separately, and/or optionally jointly) to generate corresponding per-operation energy utilization measurement output data 3616 for each sub-operation. A sub-operation measurement aggregation module 3679 can generate the per-operation energy utilization measurement data 3616 for the operation 3701.i as a whole as a function of the plurality of per-operation energy utilization measurement data 3616 for the plurality of its sub-operations (e.g. one or more values of the energy utilization measurement data 3617 for the operation 3701.i are computed as a sum of, or some other function of, corresponding values in energy utilization measurement data 3617 across all of the sub-operations 3701.i.1-3701.i.Z).

[0552] FIG. 27H illustrates an embodiment of energy utilization measurement system that generates per-operation energy utilization measurement output data 3616 for each of a plurality of operations 3701.1-3701.Y based on respective per operation energy utilization measurement input data 3612 for each of the plurality of operations 3701.1-3701.Y based on power meter measurement data 3619 collected during execution of operations 3701.1-3701.Y during temporal period 3632. For example, the power meter measurement data 3619 corresponds to and/or is utilized to determine database system energy utilization 3401, where the operation energy utilization 3402.1-3402.Y is determined in determining per-operation energy utilization output data 3616 for operations 3701.1-3701.Y based on determining which portions of database system energy utilization 3401 (as indicated in power meter measurement data 3619) are attributed to each operation (e.g. based on their respective per-operation input, for example, utilized to determine which operations were performed within which portions of the temporal period and/or did/may have had respective energy utilization/spiked in power at particular times that, when aggregated, render the total database system energy utilization 3401.

[0553] FIG. 27I illustrates an example embodiment illustrating power distribution systems 3672 of one or more data centers 3670 implementing database system 10 via computing hardware 3671 that includes a plurality of computing devices 18.1-18.N powered via one or more power supply modules of one or more power distribution systems 3672. In particular, the one or more power distribution systems 3672 can implement power monitoring modules 3674 (e.g. implemented via hardware of corresponding RPPs, PDUs, UPSs, and/or other power distribution systems), which can be operable to generate some or all power meter measurement data 3619 over time based on monitoring of and/or delivery of power to various computing devices/other computing hardware 3671 of database system 10. The power meter measurement data 3619 of FIG. 27 can implement the power meter measurement data 3619 of FIG. 27H and/or any embodiment of power meter measurement data 3619 described herein. Some or all features and/or functionality of database system 10 of FIG. 27I can be utilized to implement database system 10 of FIG. 26B.

[0554] The power meter measurement data 3619 is optionally a collection of/aggregation of a plurality of different power meter measurement data collected via a plurality of different power monitoring modules 3674 of a plurality of different power distribution systems 3672, for example, responsible for powering different portions of computing hardware 3671 (e.g. different racks/cabinets; different subsets of the plurality of computing devices 18.1 in different physical locations; different types of resources where different power meter measurement data 3619 optionally includes drive-based power meter measurement data and/or processor-based power meter measurement data and/or memory-based power meter measurement data and/or network-based power meter measurement data; and/or power via different power supply modules 3673 and/or different types of power).

[0555] FIG. 27J illustrates an embodiment where per-operation energy utilization measurement input data 3612 includes operation execution monitoring data 3659 generated, for example, during execution of operation 3701.i, where the energy utilization measurement data 3617 for operation 3701.i is generated via execution of energy utilization measurement function(s) 3649 as a function of the operation execution monitoring data 3659, alternatively or in addition to being generated as a function of some or all other input data 3612 for operation 3701.i. Some or all of the FIGS. 27K and 27L illustrates embodiments of at least one operation execution monitoring module 3639 implemented by data processing and/or storage system to generate operation execution monitoring data 3659 for a plurality of operations 3701.1-3701.Y (and/or to generate corresponding operation execution monitoring data 3629′ for a plurality of sub-operations of one or more of these operations 3701) for example, that are executing concurrently and/or are executed within a same temporal period. The operation execution monitoring module 3639 can optionally be implemented by admin data logging system 3508, for example, in conjunction with performing admin/logging operations and/or monitoring operation execution. The operation execution monitoring module 3639 can be implemented by one or more computing devices 18 of database system 10 and/or any processing/memory resources of database system 10.

[0556] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can include execution time window tracking data 3663.i. The execution time window tracking data 3663.i can indicate an execution start time 3675 indicating when execution initiated and/or can indicate an execution started flag 3677, for example, as a Boolean value indicating whether the operation has initiated execution or not. The execution time window tracking data 3663.i can alternatively or additionally indicate an execution end time 3675 indicating when execution ended and/or can indicate an execution ended flag 3679, for example, as a Boolean value indicating whether execution of the operation has ended or not.

[0557] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can alternatively or additionally include: drive utilization tracking data 3666.i (e.g. indicating how many/how long/which particular drive-based resources are accessed/read from/written to in executing the database operation 3701.i or the sub-operation 3701.i.1); processor utilization tracking data 3667.i (e.g. indicating how many/how long/which particular processor-based resources are assigned to process/are utilized in executing the database operation 3701.i or the sub-operation 3701.i.1); memory utilization tracking data 3668.i (e.g. indicating how many/how long/which particular memory-based resources are accessed/read from/written to in executing the database operation 3701.i or the sub-operation 3701.i.1); and/or chassis and/or network utilization tracking data 36679.i (e.g. indicating how many/how long/which particular network-based resources are assigned to/are utilized in executing the database operation 3701.i or the sub-operation 3701.i.1);

[0558] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can alternatively or additionally include tracked number of rows/byte read 3622′.i and/or tracked number of rows/byte written 3623′.i.

[0559] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can alternatively or additionally include disk spill tracking data 3671.i, for example, indicating whether/how much data has spilled to disk in executing the corresponding operation/sub-operation. For example, this spilling to disk and/or corresponding tracking can be performed via any embodiment of spilling to disk and/or implementing a corresponding spill to disk flag described herein.

[0560] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can alternatively or additionally include: hardware outage tracking data 3672, for example, indicating whether/which/how many computing devices 18/nodes 37/other computing hardware participating in execution of the operation experienced outages/required reassignment of respective tasks during their execution of the operation; and/or operation error and/or retry tracking data 3673.i indicating if/when/how many times an operation failed and/or required restarting/retrying via same or different hardware.

[0561] In some embodiments, some or all features and/or functionality of executing operations 3701 can be implemented via parallelized execution of tasks via a plurality of nodes, which can include assigning different tasks to different nodes for in parallel, handling of node outages and facilitating reassignment of tasks, and/or other handling of node outages and/or execution of tasks, for example, implemented via some or all features and/or functionality of assigning, executing, and/or reassigning tasks as disclosed by: U.S. Utility application Ser. No. 18/482,939, entitled “PERFORMING SHUTDOWN OF A NODE IN A DATABASE SYSTEM” filed Oct. 9, 2023, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0562] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can alternatively or additionally include mid-execution operation execution plan re-selection data 3674, for example, indicating whether/how execution of the operation changed/was reconfigured, for example, in embodiments where a plan execution of an operation (e.g. a query) can be dynamically changed mid-execution, for example, via any embodiment of dynamically selecting how a query is executed and/or prioritized described herein.

[0563] Some or all of the operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can be updated over the course of its execution, where various metrics included in the monitoring data are updated multiple times as the corresponding value changes (e.g. increases) over the course of execution.

[0564] The operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can be implemented as atomic integers, for example, assessable by a plurality of nodes/parallelized resources performing respective portions of the operation and/or sub-operation. For example, a given node/parallelized resource increments/updates the integer value by an amount corresponding to its respective participation, such as incrementing a number of rows processed (e.g. read and/or written) by a number of rows included in a batch of rows processed by the parallelized node), and/or flips a corresponding bit to one upon detecting a binary condition is true.

[0565] Some or all of the operation execution monitoring data 3659.i generated for a given operation 3701.i (and/or generate for a given sub-operation 3701.i.1 of a given operation 3701.i) can implemented as, can be included in, and/or be utilized to determine some or all of the operation parameter data 3714.

[0566] FIGS. 28A-28Q illustrate embodiments of a database system that implements an energy utilization estimation system 3551. Some or all features and/or functionality of the energy utilization estimation system 3551 of FIGS. 28A-28Q can implement the energy utilization estimation system 3551 of FIG. 26C and/or any embodiment of the energy utilization processing system 3500 described herein. Some or all features and/or functionality of the energy utilization estimation data 3571 of FIGS. 28A-28Q can implement any embodiment of energy utilization data 3510 described herein. Some or all features and/or functionality of database system 10 of FIGS. 28A-28Q can implement any embodiment of database system 10 described herein.

[0567] FIG. 28A illustrates an embodiment of an energy utilization estimation system 3551 that implements a per-operation energy utilization estimation module 3731 that executes one or more energy utilization estimation functions 3719 to generate per-operation energy utilization estimation output data 3716 that includes energy utilization estimate data 3717 for a given database operation 3701.i (e.g. a prospective operation that has not yet been performed) based on per-operation energy utilization estimation input data 3712 for the given database operation 3701.i.

[0568] In some embodiments, the energy utilization estimation system 3551 implements some or all features and/or functionality of energy utilization measurement system 3550 to perform energy utilization estimation function(s) 3719 in a same or similar fashion as performance of energy utilization measurement function(s) 3649 to generate per-operation energy utilization estimation output data 3716, which can be implemented in a same or similar fashion as per-operation energy utilization measurement output data 3616, based on per-operation energy utilization estimation input data 3712, which can be implemented in a same or similar fashion as per-operation energy utilization measurement input data 3612. For example, the energy utilization measurement data 3617 is implemented as an estimate vs. a definitive measurement as discussed previously, despite the operation having already been performed, and the energy utilization estimate data 3717 can be generated for operations not yet performed based on same or similar input data as energy utilization measurement data 3617 (e.g. input data 3712 can be implemented to include some or all input data 3612 that is determined prior to the execution of the database operation 3701.i and/or estimates/projected values for some or all input data 3612 that is determined after to the execution of the database operation 3701.i).

[0569] In some embodiments, the energy utilization measurement system 3550 can optionally be implemented by energy utilization estimation system 3551, optionally processing additional and/or more precise information in input data 3712 in the case where the operation has already been executed vs. not having this information/having projected values for this information in input data 3712 in the case where the operation has not yet been executed. Alternatively or in addition, any of the measurements/measurement data described herein can be implemented as estimates/estimate data, regardless of whether the operation was already executed or has yet to be executed.

[0570] The one or more energy utilization estimation functions 3719 can be executed based on applying corresponding parameters, weights, and/or function definition(s) that are: received by energy utilization processing system 3500; accessed in memory by energy utilization processing system 3500; configured via user input by a user entity communicating with energy utilization processing system 3500; automatically generated and/or automatically updated/re-tuned over time by energy utilization processing system 3500 (e.g. via training on training data to generate a corresponding machine learning model and/or artificial intelligence (AI) model based on utilizing at least one machine learning-based training function and/or technique and/or based on utilizing at least one AI-based training function and/or technique); implemented by energy utilization processing system 3500 via artificial intelligence (e.g. based on utilizing a generative AI platform and/or other AI platform/model(s) accessible by and/or communicating with by energy utilization processing system 3500); and/or otherwise being determined by energy utilization processing system 3500. The corresponding parameters, weights, and/or function definition(s) of energy utilization estimation function(s) 3719 can be configured to generate per-operation energy utilization estimation output data 3716 as a function (e.g. deterministic function) of corresponding per-operation energy utilization estimation input data 3712.

[0571] The energy utilization estimation output data 3716 for operation 3701.i can include energy utilization estimate data 3717 for the given operation 3701.i, which can indicate one or more energy utilization values 3718 (e.g. corresponding to any of the energy utilization-based metrics described herein). Energy utilization estimate data 3717 of FIG. 28A can include any values of the example energy utilization measurement output data 3616 presented in FIG. 27C and/or the energy utilization estimate data 3717 can be implemented in a same or similar fashion (and/or can include values for same or similar metrics) as any embodiment of energy utilization measurement data 3617 described herein.

[0572] The energy utilization estimation input data 3712 for operation 3701.i can indicate an operation type 3713 for the operation (e.g. whether the operation is a query operation 2702, ingress operation 2703, storage-formatted data generation operation 2704, rebuilding operation 2705, migration operation 2706, admin data logging operation 2707, another operation, a sub-operation of one of these operation categories, etc.). For example, the operation type 3713 indicates a value denoting an identifier for the respective operation type of operation 3701.i. The one or more energy utilization values 3718 of energy utilization estimate data 3717 can be computed by energy utilization estimation system 3551 as a function of the operation type 3713.

[0573] The energy utilization estimation input data 3712 for operation 3701.i can alternatively or additionally indicate operation parameter data 3714 further specifying factors relating to execution of the given operation, for example, that impact energy utilization in executing the operation 3701. Some or all operation parameter data 3714 can be determined prior to execution of the operation 3701, for example, as specified in configurable arguments and/or executable expression of a corresponding request to execute the operation 3701.

[0574] Operation parameter data 3714 of FIG. 28A can include any values of the example operation parameter data 3714 presented in FIG. 27D and/or the operation parameter data 3714 of FIG. 28A can be implemented in a same or similar fashion (and/or can include values for same or similar metrics) as any embodiment of operation parameter data 3714 described herein. The one or more energy utilization values 3718 of energy utilization estimate data 3717 can be computed by energy utilization estimation system 3551 as a function of the operation parameter data 3714.

[0575] The energy utilization estimation input data 3712 for operation 3701.i can alternatively or additionally indicate a projected time window 3705 when execution of the given database operation 3701.i is expected to be performed (e.g. amount of time/delay from the current time, a scheduled time for execution, and expected time window in which the operation is expected to be executed). The one or more energy utilization values 3718 of energy utilization estimate data 3717 can be computed by energy utilization estimation system 3551 as a function of the projected time window 3705.

[0576] The energy utilization estimation input data 3712 for operation 3701.i can alternatively or additionally indicate projected database condition data 3715 during execution of operation 3701.i (e.g. current database condition data, or database condition data projected for projected time window 3705) further specifying factors relating to the state of database system 10 at the time the operation is expected to be executed, for example, that impact energy utilization in executing the operation 3701. This can include information such as: database system wide energy utilization (e.g. corresponding values for any metrics described herein), type of power (e.g. battery vs. grid-based vs. renewable) known/expected to be used by the database at the time the operation is projected to be executed; a known/expected mode of operation of storage of the database in persistently storing data 2711 at the time the operation is projected to be executed; an emissions factor for the database's current mode of operation/functionality at the time the operation is projected to be executed; a known/expected pricing scheme at the time the operation is projected to be executed; configuration of the database system 10 at the time the operation is projected to be executed; how much data 2711 is known/expected to be stored across how many tables across how many devices at the time the operation is projected to be executed; which nodes/devices are known/expected to be online vs offline/active vs. idle at the time the operation is projected to be executed; number/type/parameters/energy utilization of other operations projected to be executing concurrently/pending executed/requested for execution when the operation 3701.i is executed, etc. The one or more energy utilization values 3718 of energy utilization estimate data 3617 can be computed by energy utilization estimation system 3551 as a function of the projected database condition data 3715.

[0577] The energy utilization estimation input data 3712 for operation 3701.i can alternatively or additionally include power usage policy data 3818 that is currently in place or projected to be in place during the projected time window. For example, the power usage policy data 3818 can be implemented to impose restrictions on whether/when/how the corresponding operation 3701.i can be executed by database system 10, as discussed in further detail herein. Adherence to such restrictions can thus impact the energy utilization induced in executing the database operation. The one or more energy utilization values 3718 of energy utilization estimate data 3617 can be computed by energy utilization estimation system 3551 as a function of the power usage policy data 3818.

[0578] The values 3718 of energy utilization estimate data can correspond to singular values for energy utilization (e.g. for of the energy utilization-based metrics), for example, based on the estimation generated via energy utilization estimation function being known/expected to be accurate and/or a singular estimated value being sufficient (e.g. a mean/center of a corresponding distribution, given the input data 3712). These can alternatively or additionally correspond to value ranges (e.g. bounded range by min and max value, confidence intervals, range having a center and span dictated by the input data 3712, for example, based on how confident the estimate is based on the input data 3712, etc.) for energy utilization (e.g. for of the energy utilization-based metrics), for example, based on guaranteeing/expecting the actual value to fall within the presented range. These can alternatively or additionally correspond to probability distribution data (e.g. expected value and/or standard deviation for the value given the input data 3712, a probability mass function (PMF) and/or probability density function (PDF) for the value, given the input data 3712, and/or other distribution data).

[0579] In some embodiments, the energy utilization estimate data 3717 can characterize an amount/portion of energy utilization by the database system 10 attributed to execution of the particular database operation 3701.i. For example, if value Y is value 3718 estimated to be energy utilization consumed by the database operation, and if energy utilization measured for some or all of the database system as a whole during a temporal period while the operation ultimately executes is measured/determined to be a value X (e.g. for one or more energy utilization metrics, optionally indicated by power meter measurement data 3619 captured over the temporal period) across a temporal period in which database operation 3701.i is ultimately executed, a value Z=X−Y is thus expected to be the energy utilization that would have been expected to have been consumed over the temporal period if the database operation had not been executed. As another example, if values Y1, Y2, . . . YY correspond to values 3718 estimated to be energy utilization consumed by Y different operations 3701.1-3701.Y executed over the temporal period, the value of X is expected to be an aggregation of (e.g. summation of or other function of) Y1−YY.

[0580] In some cases, estimation error can be measured based on retroactively generating energy utilization measurement data 3617 for the given operation via the energy utilization measurement system 3550, where difference in value(s) 3718 between the energy utilization estimate data and energy utilization measurement data (e.g. when energy utilization measurement data is known/expected to be accurate or close to accurate) can correspond to an amount of error in the estimation. As another example, measuring error can include measuring a difference between: the aggregation of Y1 through YY, and X (e.g. as indicated in power meter measurement data 3619). Measuring such error for many operations 3701 having energy utilization estimate data generated and energy utilization measurement data generated can be utilized to characterize error of/accuracy of the energy utilization estimation function(s) 3719, which can be utilized to configure width/magnitude of ranges/confidence intervals/standard deviation in values 3718 of energy utilization estimate data 3717.

[0581] FIG. 28B illustrates an example of energy utilization estimate data 3717 of energy utilization estimate output data 3716 for operation 3701.i generated by energy utilization estimation system 3551. The energy utilization estimate data 3717 can include total energy estimate data 3780, peak power estimate data 3781, temporal energy utilization distribution estimate data 3782, and/or resource type-based energy utilization estimate data 3783.

[0582] The total energy estimate data 3780 can characterize how much energy, and/or associated monetary cost, is estimated to be required to execute the database operation 3701.i over the duration of the database operation (e.g. as a portion of all energy consumed by the database system during the temporal period in which the database operation is executed). The total energy estimate data 3780 can indicate an estimated value for total energy utilization amount 3784 (e.g. a singular value) corresponding to a value indicating estimated total amount of energy utilized (e.g. expressed in kilowatt-hours, measure of energy, integral and/or summation of power utilization by the database operation over a corresponding temporal period in which the database operation was executed, and/or as a value for any of the energy utilization-based metrics described herein). The total energy estimate data 3780 can alternatively or additionally include an estimated value for total energy utilization cost 3785, which can indicate a total energy utilization cost (e.g. a singular value, for example, corresponding to estimated price/monetary/carbon credit/carbon offset) corresponding to a value indicating cost/price of the total amount of energy utilized. The total energy estimate data 3780 can alternatively or additionally include an estimated value range for energy utilization amount and/or cost 3786 corresponding to a range (e.g. bounded by max and min values, a confidence interval, etc.) of value that the actual value for total energy utilization amount and/or total energy utilization cost is known/expected to fall within. The total energy estimate data 3780 can alternatively or additionally include probability distribution data (e.g. expected value and/or standard deviation, parameters defining a PDF or PMF for the corresponding distribution curve, etc.) for estimated total energy utilization amount and/or cost 3787.

[0583] The peak power estimate data 3781 can characterize a maximum amount of power, and/or associated monetary cost, that is estimated to be required to execute the database operation 3701.i at any given time during the temporal period in which the database operation is executed. In some cases, peak power of the database system as a whole occurs at this time (e.g. the spike in power required at the given time to execute database operation 3701.i is substantial enough to render corresponding peak power across the database system during the temporal period in which the database operation is executed, and/or across a longer period of time, for example, due to being more significant than other concurrent activities by the database system over the temporal period and/or more significant than additional activities over the longer period of time). In other cases, peak power of the database system occurs at a different time (e.g. the peak power for the operation was not substantial enough to render peak power by the database system as a whole at that time, for example, due to other concurrently executed database operations with their own spikes in power also having been executing at different times, having been load balanced such that various peak powers of various database operations did not compound, another database operation having a larger peak power during a different time in the temporal period, etc.).

[0584] The peak power estimate data 3781 can include an estimated value for peak power amount 3788 (e.g. a singular value, expressed in kilowatts, corresponding to an estimated maximum power induced by the database operation 3701.i over a temporal period in which the database operation is executed, optionally expressed in kilowatt-hours or other energy measure for a small time window (e.g. a second or fraction of a second) within the temporal period the database operation is executed having highest energy consumption over all time windows within the temporal period, and/or as a value for any of the energy utilization-based metrics described herein). The peak power estimate data 3781 can include an estimated value for peak power cost 3789, which can be indicate estimated cost attributed to the peak power amount (e.g. a singular value, for example, corresponding to price/monetary/carbon credit/carbon offset). The total energy estimate data 3771 can alternatively or additionally include an estimated value range for peak power amount and/or cost 3790 corresponding to a range (e.g. bounded by max and min values, a confidence interval, etc.) of value that the actual value for peak power amount and/or peak power cost is known/expected to fall within. The total energy estimate data 3781 can alternatively or additionally include probability distribution data (e.g. expected value and/or standard deviation, parameters defining a PDF or PMF for the corresponding distribution curve, etc.) for estimated total peak power amount and/or cost 3791.

[0585] The temporal energy utilization distribution estimate data 3782 can characterize estimated power consumption by the database operation over time, for example, based on an estimated execution duration of time indicating how long the execution of database operation 3701.i will last (e.g. length of the corresponding temporal period in which the database operation 3701.i is executed). This can characterize when power is estimated to spike/dip during execution of the database operation, for example, based on some portions of the database operation's execution being expected to require more power than others.

[0586] The temporal energy utilization distribution estimate data 3782 can include estimated absolute peak power timing data 3792 indicating when the peak power of the database operation is estimated to occur, for example, in a standardized time measure across the database system 10 (e.g. a time in coordinated universal time (UTC) time; in the daytime vs. in the nighttime; over the weekend vs. during a weekday, etc. (e.g. expressed as a singular time value, time range, and/or probability distribution value for the absolute time). The temporal energy utilization distribution estimate data 3782 can alternatively or additionally include estimated relative peak power timing data 3793 indicating when the peak power is estimated to occur relative to the temporal period in which the database operation was executed (e.g. after 3 seconds of execution; when the operation is 20% complete; after 15% of the total duration of the database operation execution elapses, etc.; expressed as a singular time value, time range, and/or probability distribution value for the absolute time). The temporal energy utilization distribution estimate data 3782 can alternatively or additionally include distribution of power consumption over the execution duration 3794 (e.g. power utilization attributed to the database operation execution across a plurality of instantaneous points in time during an estimated temporal period of execution, energy utilization across a plurality of clock cycles/short time windows within the temporal period, a function definition defining a corresponding curve for power consumption as a function of time, etc.), and/or can otherwise indicate absolute/relative times that other spikes in power consumption induced by the database operation are estimated to occur (e.g. over a predetermined threshold amount), absolute/relative times that dips in power are estimated to (e.g. under a predetermined threshold amount), etc. (e.g. expressed as a singular time values, time ranges, and/or probability distribution value for the absolute times, mapped to corresponding power levels).

[0587] The resource-based energy utilization estimate data 3783 can characterize how energy utilization by the database operation's execution is estimated to be dispersed across different resources of the database system. This can be useful in identifying which resources are expected to experience the greatest power draw, power spikes, and/or highest contribution to energy utilization cost in executing the corresponding database operation.

[0588] The resource-based energy utilization estimate data 3783 can include drive-based energy utilization estimate data 3795 indicating drive-based energy utilization estimated to be induced via execution of the database operation, such as energy utilization by storage devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve storing and/or accessing data (e.g. via IO operators and/or execution of an IO pipeline) in these storage devices and/or correspond to operations involving persistent storage of data. The drive-based energy utilization estimate data 3795 can include energy utilization estimate data 3780, peak power estimate data 3781, and/or temporal energy utilization distribution estimate data 3782 attributed specifically to drive-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to drive-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to drive-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to drive-based resources; etc.). The drive-based energy utilization estimate data 3795 can optionally further indicate distribution of such drive-based energy consumption across different types of storage devices.

[0589] The resource-based energy utilization estimate data 3783 can include processor-based energy utilization estimate data 3796 indicating processor-based energy utilization estimated to be induced via execution of the database operation, such as energy utilization by processor devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve processing data via these processing devices. The processor-based energy utilization estimate data 3795 can include energy utilization estimate data 3780, peak power estimate data 3781, and/or temporal energy utilization distribution estimate data 3782 attributed specifically to processor-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to processor-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to processor-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to processor-based resources; etc.). The processor-based energy utilization estimate data 3796 can optionally further indicate distribution of such processor-based energy consumption across different types of processors (e.g. different types of processing devices, different types of processing cores within multi-core processing devices etc.).

[0590] The resource-based energy utilization estimate data 3783 can include memory-based energy utilization estimate data 3797 indicating memory-based (e.g. for non-storage-based memory) energy utilization estimated to be induced via execution of the database operation, such as energy utilization by memory devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve storing intermediate data (e.g. hash maps, pages of rows, etc.) generated in executing the database operation via these memory devices. The memory-based energy utilization estimate data 3797 can include energy utilization estimate data 3780, peak power estimate data 3781, and/or temporal energy utilization distribution estimate data 3782 attributed specifically to memory-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to memory-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to memory-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to memory-based resources; etc.). The memory-based energy utilization estimate data 3797 can optionally further indicate distribution of such memory-based energy consumption across different types of memory (e.g. RAM vs. cache memory, etc.).

[0591] The resource-based energy utilization estimate data 3783 can include chassis and/or network-based energy utilization estimate data 3798 indicating network-based/chassis-based energy utilization estimated to be induced via execution of the database operation, such as energy utilization by network devices of database system 10 in executing the given database operation, for example, based on the database operation 3701.i including steps that involve communicating data between devices (e.g. between nodes 37 at same or different levels of a query execution plan, etc.) and/or involve accessing external networks (e.g. the internet), in executing the database operation via these network devices. The network-based energy utilization estimate data 3798 can include energy utilization estimate data 3780, peak power estimate data 3781, and/or temporal energy utilization distribution estimate data 3782 attributed specifically to network-based resources (e.g. total energy utilization amount/cost value/range/probability distribution data attributed specifically to network-based resources; peak power amount/cost value/range/probability distribution data attributed specifically to network-based resources; peak power timing/power distribution values, ranges, and/or probability distribution data attributed specifically to network-based resources; etc.). The network-based energy utilization estimate data 3798 can optionally further indicate distribution of such network-based energy consumption across different types of network devices.

[0592] In some embodiments, one or more values of energy utilization estimate data 3717 is generated as a function of and/or based on implementing some or all features and/or functionality of query processing cost estimate data 3141 (e.g. memory usage estimate 3012; internal runtime estimate 3013; external runtime estimate 3014)); query processing cost estimator module 3115; query processing tracking module 3152; query data 2914, execution start time 3015 as disclosed by U.S. Utility application Ser. No. 16/720,481, entitled “SELECTING A NORMALIZED FORM FOR CONVERSION OF A QUERY EXPRESSION”, filed Dec. 19, 2019, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

[0593] FIG. 28C illustrates an embodiment of energy utilization estimation system 2551 that implements: an ingress operation energy utilization estimation module 3740 to generate ingress operation energy utilization estimation data 3573 for some or all ingress operations 2703 executed via data ingress system 3511; a storage-formatted data generation and/or storage operation energy utilization estimation module 3750 to generate storage-formatted data generation and/or storage operation energy utilization estimation data 3574 for some or all storage-formatted data generation and/or storage operations 2704 executed via storage-formatted data generation and/or storage system 3517; a rebuilding operation energy utilization estimation module 3760 to generate rebuilding operation energy utilization estimation data 3575 for some or all rebuilding operations 2705 executed via rebuilding system 3507; a migration operation energy utilization estimation module 3770 to generate migration operation energy utilization estimation data 3576 for some or all migration operations 2706 executed via migration system 3509; and/or a query operation energy utilization estimation module 3730 to generate query operation energy utilization estimation data 3572 for some or all query operations 2702 executed via query processing system 2502.

[0594] FIG. 28D illustrates an embodiment of a query operation energy utilization estimation module 3730 that performs one or more query operation energy utilization estimation functions 3739 to generate energy utilization estimate data 3717 in query operation energy utilization estimation output data 3736 for a query operation 2702.i, for example, as a function of query operation energy utilization input data 3732 for query operation 2702.i, which can include input specific to execution of a query operation and/or input influencing energy utilization of a query operation, such as query operation type 3733 (e.g. a sub-type of operation type 3713 specific to query operations), query operation parameter data 3734 (e.g. indicating parameters of operation parameter data 3714 specific to execution of query operations), query execution projected database condition data 3735 (e.g. indicating projected database condition data 3715 relevant to execution of query operations), and/or any other energy utilization estimation input data 3712 relevant to energy utilization in executing a query operation. For example, the query operation energy utilization estimation functions 3739 are a configured type of energy utilization estimation function 3719 that is tuned specifically for query operations (e.g. implements a model trained via training data corresponding specifically to historically executed query operations), where any performance of energy utilization estimation function 3719 described herein can optionally include performance of one or more query operation energy utilization estimation functions 3730 based on the operation 3701.i being/including a query operation 2702.

[0595] FIG. 28E illustrates an embodiment of an ingress operation energy utilization estimation module 3740 that performs one or more ingress operation energy utilization estimation functions 3749 to generate energy utilization estimate data 3717 in ingress operation energy utilization estimation output data 3746 for a ingress operation 2703.i, for example, as a function of ingress operation energy utilization input data 3742 for ingress operation 2703.i, which can include input specific to execution of a ingress operation and/or input influencing energy utilization of a ingress operation, such as ingress operation type 3743 (e.g. a sub-type of operation type 3713 specific to ingress operations), ingress operation parameter data 3744 (e.g. indicating parameters of operation parameter data 3714 specific to execution of ingress operations), ingress execution projected database condition data 3745 (e.g. indicating projected database condition data 3715 relevant to execution of ingress operations), and/or any other energy utilization estimation input data 3712 relevant to energy utilization in executing a ingress operation. For example, the ingress operation energy utilization estimation functions 3740 are a configured type of energy utilization estimation function 3719 that is tuned specifically for ingress operations (e.g. implements a model trained via training data corresponding specifically to historically executed ingress operations), where any performance of energy utilization estimation function 3719 described herein can optionally include performance of one or more ingress operation energy utilization estimation functions 3740 based on the operation 3701.i being/including an ingress operation 2703.