Patent Application
20180341676
The subject matter described herein relates to database management and, in particular, query optimization.
Database management systems have become an integral part of many computer systems. For example, some systems handle hundreds if not thousands of transactions per second. On the other hand, some systems perform very complex, multidimensional analysis on data. In both cases, the underlying database may need to handle responses to queries very quickly in order to satisfy systems requirements with respect to transaction time. Given the complexity of these queries and/or their volume, the underlying databases face challenges when optimizing performance.
In some aspects, a method, computer program product, and system are provided. In some implementations, there may be provided a method including detecting a select query as a candidate for optimization, the select query including an order by, an offset value, and a limit value; determining, in response to the detecting, a modified offset value as the difference between the offset value and a size of a smaller dataset; and performing the select query to form a result set, the select query executed based on at least the modified offset value.
In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The select query may be executed on a larger dataset by at least skipping to the determined modified offset in the larger dataset. The smaller dataset may be merged with a remaining portion of the larger dataset to form the result set. The remaining portion may result from at least skipping to the determined modified offset in the larger dataset. The select query may be received from an application. The select query may be received as a candidate for optimization. The result set (which may be determined based at least on the modified offset) may be returned to the application. The smaller dataset may represent a first portion of a database and the larger data set may represent a second portion of a database. The first portion may represent a plurality of rows of the database, and the second portion may represent a plurality of other rows of the database. The order by may specify result ordering. The offset value may specify how many rows to skip. The limit value may specify a maximum quantity of elements for the result set. The executing the select query may further include pushing down to the determined modified offset in the larger dataset.
Implementations of the current subject matter can include systems and methods consistent with the present description, including one or more features as described, as well as articles that comprise a tangibly embodied machine-readable medium operable to cause one or more machines (e.g., computers, etc.) to result in operations described herein. Similarly, computer systems are also described that may include one or more processors and one or more memories coupled to the one or more processors. A memory, which can include a computer-readable storage medium, may include, encode, store, or the like one or more programs that cause one or more processors to perform one or more of the operations described herein. Computer implemented methods consistent with one or more implementations of the current subject matter can be implemented by one or more data processors residing in a single computing system or multiple computing systems. Such multiple computing systems can be connected and can exchange data and/or commands or other instructions or the like via one or more connections, including but not limited to a connection over a network (e.g. the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, or the like), via a direct connection between one or more of the multiple computing systems, etc.
The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims. While certain features of the currently disclosed subject matter are described for illustrative purposes in relation to an enterprise resource software system or other business software solution or architecture, it should be readily understood that such features are not intended to be limiting. The claims that follow this disclosure are intended to define the scope of the protected subject matter.
The accompanying drawings, which are incorporated in and constitute a part of this specification, show certain aspects of the subject matter disclosed herein and, together with the description, help explain some of the principles associated with the disclosed implementations. In the drawings,
When practical, similar reference numbers denote similar structures, features, or elements.
Suppose a select query is performed over, for example, two horizontal partitions, such as shards or fragments, of a database table, and further suppose the select includes an order by command that sorts the result set in ascending (or descending) order on a given column attribute(s) and the select further includes an offset clause and a limit clause. The offset defines how many rows should be skipped in the sorted dataset, and the limit defines how many rows should be produced, or included, in the result set being returned in response to the select query (e.g., the maximum number of results in the result set). Table 1 below depicts an example of pseudo code consistent with this example.
To illustrate further, suppose M in this example corresponds to the sorted intermediate result set for the first shard and includes 1050 elements, and N in this example corresponds to the sorted intermediate result set for the second shard and includes 10 elements. This example illustrates that there are two sorted data sets (which in this example is sorted in ascending order in accordance with Table 1). However, to return the final result set, M and N need to be merged as the order of the elements in M relative to those in N is unknown.
To illustrate further,
One way to handle the select query (which has the order by ascending, offset, and limit as shown in Table 1, for example) is to get the offset plus limit of the smallest elements of M (which returns 1002 elements), get the offset plus limit of the smallest elements of N (which returns 10 elements), merge both results, drop the offset, smallest elements from the resulting merged result, and then apply the limit. However, this would require, in this example, a comparison of up to 1012 elements to merge N into M. This merging can be very costly from a computational processing and memory perspective. Furthermore, this approach may request an initial retrieve of 1002 elements from M, which can also be costly.
In some example embodiments, a modified offset may be determined before executing the query on the larger dataset, and this modified offset may be used as the offset in the select query including an order by, offset, and limit as shown in Table 1, for example. The modified offset may be passed (or “pushed down”) to that query for more efficient runtime or execution.
Referring to the previous example, the smaller of the two datasets, such as N, may be selected. In this example, there are 10 sorted data elements in N. However, now a modified offset may be applied to the larger dataset M (or the query which produces it). This modified offset is equal to the original offset minus the size of the first, smaller dataset N:
Modified offset=MAX(0;original offset−N) Equation 1.
Referring again to the ongoing example, the modified offset is equal to 990 (which is the original offset of 1000 minus the size of the smaller dataset N of 10). In this example, regardless of how the elements of M and N are combined in the final, ordered result set, the smallest 990 elements of M cannot be in the final result set (as N only has 10 elements and the skipping of the 1000 elements of the merged result of M and N). As such, the first 990 data elements of M can be skipped early. If M is produced by a separate query procedure, this offset of 990 can be pushed down to that separate query routine for runtime or execution, which may exploit the modified offset to produce fewer intermediate results (which may be obtained faster and with less processing and memory burden). Here, the comparisons of N to M to merge the datasets into the final result set may include only 22 comparisons, for example. Specifically, the elements of the dataset N are compared with the elements 990 to 1002 (which is the original offset of 1000 plus the original limit of 2) of the M dataset. This reduction can save a considerable amount of processing and/or memory resources.
At 210-220, the query optimizer 110 may receive a select query from application 105, and may then determine whether the select query includes order by, offset, and limit commands. For example, if a select query includes the order by, offset, and limit, then the select query is a candidate for optimization by the query optimizer. To illustrate further, the select query may have the form shown in Table 1 above. At 230, the query optimizer 110 may select a smaller of the two datasets. Referring to the example above, the query optimizer may select the smaller N dataset (which has 10 elements) rather than the larger M dataset (which has 1050 elements). Here, the smaller dataset, N, is selected, and the offset or limit is not applied to the smaller, N dataset. The selected dataset may then be processed by the select query having order by ascending and a offset and limit as shown in Table 1, for example.
At 240, the query optimizer 110 may determine a modified offset for the larger dataset. For example, the modified offset may be determined, based on Equation 1, as the original offset minus the size of the selected, smaller dataset. Referring to the example above, the modified offset is 990 (1000−10).
At 250, the query optimizer 110 may execute the select query using the determined modified offset. For example, the query optimizer 110 may pushdown the select query using the determined modified offset on the larger dataset. For example, the query optimizer 110 may push down on the stack including larger, dataset M to the modified offset of 990, skipping thus to the 990th element of the M dataset), so the order by for column M has the following form: ORDER BY M, Ascending, Modified Offset=990 and limit=2.
At 260, the query optimizer 110 may merge the shorter result set with the pushed down larger result set. For example, the query optimizer 110 may merge the shorter result set N with the pushed down larger result set M to determine the final, sorted result set. This merge may compare the 10 elements of the shorter dataset N with the 990th element through 1002nd element of the larger dataset M (for example, in order to determine where the elements of the N dataset should be merged in the sequence of dataset M). The 1002nd element of the larger dataset M represents the original offset of 1000 plus the limit of 2.
After the merge, the query optimizer 110 may return, at 270, the final result set to the application 105. This final result set includes, in this example, two elements, as the limit in this example is two.
Although process 200 refers to two datasets, wherein one has a larger quantity of elements than the other, the two datasets may be of any size including equal size as well. Moreover, the process may be applied to more than two data sets as well. In the case of more than two datasets, the process 200 may be applied repeatedly or recursively. Although the example of Table 1 refers to a column, the optimization described herein may be performed for other portions of a database as well as for other types of datasets in which a merging of the datasets is performed. Furthermore, the example select at Table 1 is merely for illustrative purposes as the select may for example perform an order by over more than one column or the sort may be descending.
As illustrated, computing apparatus 300 may include one or more processors such as processor 310 to execute instructions that may implement operations consistent with those described herein. Apparatus 300 may include memory 320 to store executable instructions and/or information. Memory 320 may include solid-state memory, solid-state disk drives, magnetic disk drives, or any other information storage device. Apparatus 300 may include one or more network interfaces, such as network interface 340, which can be configured to communicate over wired networks and/or wireless networks. Wireless networks may include WiFi, WiMax, Bluetooth, and cellular networks (2G/3G/4G/5G), and/or any other wireless network. In order to effectuate wireless communications, the network interface 340, for example, may utilize one or more antennas, such as antenna 390.
Apparatus 300 may include one or more user interface, such as user interface 350. The user interface 350 can include hardware or software interfaces, such as a keyboard, mouse, or other interface, some of which may include a touchscreen integrated with a display 360. In various implementations, the user interface 350 can include one or more peripheral devices and/or the user interface 350 may be configured to communicate with these peripheral devices.
The apparatus 300 may also comprise an input and output filter 330, which can filter information received from and/or transmitted to a user interface 350, a network interface 340, and/or the like. The apparatus 300 may be powered through the use of one or more power sources, such as power source 370. One or more of the components of the apparatus 300 may be cooled off through the use of one or more heat sinks, such as heat sink 380. As illustrated, one or more of the components of the apparatus 300 may communicate and/or receive power through a system bus 399.
In some implementations, the computing apparatus 300 can be used to implement at least a portion of a database management system. In some aspects, a database management system may be a hardware and/or software system for receiving, handling, optimizing, and/or executing database queries. In some aspects, a database, as referred to herein, can be a structured, organized collection of data, such as schemas, tables, queries, reports, views, and/or the like, which may be processed for information. A database may be physically stored in a hardware server or across a plurality of hardware servers. In some aspects, a database management system may be a hardware and/or software system that interacts with a database, users, and/or other software applications for defining, creating, updating the structured data, and/or for receiving, handling, optimizing, and/or executing database queries.
For example, the computing apparatus 300 can provide one or more features of a high-level programming software system or other software that includes database management features. The computing apparatus 300 can also aggregate or otherwise provide a gateway via which users can access functionality provided by one or more external software components. One or more client machines can access the computing apparatus 300, either via a direct connection, a local terminal, or over a network (e.g. a local area network, a wide area network, a wireless network, the Internet, or the like).
The computing apparatus 300 can be configured to access a database that includes at least one table, which can in turn include at least one column. The database table can store any kind of data, potentially including but not limited to definitions of scenarios, processes, and one or more configurations as well as transactional data, metadata, master data, etc. relating to instances or definitions of the scenarios, processes, and one or more configurations, and/or concrete instances of structured data, such as objects that are relevant to a specific instance of a scenario or a process, and the like. The database can be external to the computing apparatus 300 or may be part of the computing apparatus 300 (e.g., at least partially stored in the memory 320). In some aspects, the memory 320 may be utilized to store at least a portion of a database and/or function as an in-memory database.
For example, a processor 310, a network interface 340, and/or a user interface 350 may be configured to receive and/or load a database table or other comparable data set, into the memory 320 (e.g., in response to receipt of a query instantiated by a user or computer system through one or more client machines, external software components, core software platforms, and/or the like).
One or more aspects or features of the subject matter described herein can be realized in digital electronic circuitry, integrated circuitry, specially designed application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) computer hardware, firmware, software, and/or combinations thereof. These various aspects or features can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. The programmable system or computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
These computer programs, which can also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in any high-level programming language (e.g., following procedural and/or object-oriented programming language paradigms), and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device, such as for example magnetic discs, optical disks, memory, and Programmable Logic Devices (PLDs), used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. The machine-readable medium can store such machine instructions non-transitorily, such as for example as would a non-transient solid-state memory or a magnetic hard drive or any equivalent storage medium. The machine-readable medium can alternatively or additionally store such machine instructions in a transient manner, such as for example as would a processor cache or other random access memory associated with one or more physical processor cores.
To provide for interaction with a user, one or more aspects or features of the subject matter described herein can be implemented on a computer having a display device, such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) or a light emitting diode (LED) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, such as for example visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including, but not limited to, acoustic, speech, or tactile input. Other possible input devices include, but are not limited to, touch screens or other touch-sensitive devices such as single or multi-point resistive or capacitive trackpads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like.
The subject matter described herein can be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. The implementations set forth in the foregoing description do not represent all implementations consistent with the subject matter described herein. Instead, they are merely some examples consistent with aspects related to the described subject matter. Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations can be provided in addition to those set forth herein. For example, the implementations described above can be directed to various combinations and sub-combinations of the disclosed features and/or combinations and sub-combinations of several further features disclosed above. In addition, the logic flows depicted in the accompanying figures and/or described herein do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Other implementations may be within the scope of the following claims.
The illustrated methods are exemplary only. Although the methods are illustrated as having a specific operational flow, the order of the operations may be altered, two or more operations may be combined into a single operation, a single operation may be performed in two or more separate operations, one or more of the illustrated operations may not be present in various implementations, and/or additional operations which are not illustrated may be part of the methods.
