Patent Application
20160344788
The present disclosure relates generally to the field of stream computing, and more particularly to computing applications that receive streaming data and process the data as it is received.
Database systems are typically configured to separate the process of storing data from accessing, manipulating, or using data stored in a database. More specifically, database systems use a model in which data is first stored and indexed in a memory before subsequent querying and analysis. In general, database systems may not be well suited for performing real-time processing and analyzing streaming data. In particular, database systems may be unable to store, index, and analyze large amounts of streaming data efficiently or in real time.
Aspects of the disclosure provide a method, system, and computer program product for processing data. The method, system, and computer program product may include receiving at a first stream operator, a first tuple from a stream of tuples. In response to receiving the first tuple, port mutability conditions for a first stream operator and port mutability conditions for a second stream operator may be analyzed. From the first tuple received at the first stream operator, a first set of attribute mutability conditions may be identified. Based on the first set of attribute mutability conditions and further based on the port mutability conditions for the first stream operator and the port mutability conditions for the second stream operator, a reference to an attribute from the first tuple may be generated. In response to generating the reference, the attribute from the first tuple may be replaced with the reference to the attribute by adding the reference to a second tuple passing from the first stream operator to the second stream operator.
The above summary is not intended to describe each illustrated embodiment or every implementation of the present disclosure.
The drawings included in the present application are incorporated into, and form part of, the specification. They illustrate embodiments of the present disclosure and, along with the description, serve to explain the principles of the disclosure. The drawings are only illustrative of certain embodiments and do not limit the disclosure.
While the embodiments described herein are amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the particular embodiments described are not to be taken in a limiting sense. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.
Aspects of the present disclosure relate generally to stream computing. In embodiments, more particular aspects relate to tuple attribute copying for mutable stream operator ports. While the present disclosure is not necessarily limited to such applications, various aspects of the disclosure may be appreciated through a discussion of various examples using this context.
Stream-based computing and stream-based database computing are emerging as a developing technology for database systems. Products are available which allow users to create applications that process and query streaming data before it reaches a database file. With this emerging technology, users can specify processing logic to apply to inbound data records while they are “in flight,” with the results available in a very short amount of time, often in fractions of a second. Constructing an application using this type of processing has opened up a new programming paradigm that will allow for development of a broad variety of innovative applications, systems, and processes, as well as present new challenges for application programmers and database developers.
In a stream computing application, stream operators are connected to one another such that data flows from one stream operator to the next (e.g., over a TCP/IP socket). When a stream operator receives data, it may perform operations, such as analysis logic, which may change the tuple by adding or subtracting attributes, or updating the values of existing attributes within the tuple. When the analysis logic is complete, a new tuple is then sent to the next stream operator. Scalability is achieved by distributing an application across nodes by creating executables (i.e., processing elements), as well as replicating processing elements on multiple nodes and load balancing among them. Stream operators in a stream computing application can be fused together to form a processing element that is executable. Doing so allows processing elements to share a common process space, resulting in much faster communication between stream operators than is available using inter-process communication techniques (e.g., using a TCP/IP socket). Further, processing elements can be inserted or removed dynamically from an operator graph representing the flow of data through the stream computing application. A particular stream operator may not reside within the same operating system process as other stream operators. In addition, stream operators in the same operator graph may be hosted on different nodes, e.g., on different compute nodes or on different cores of a compute node.
Data flows from one stream operator to another in the form of a “tuple.” A tuple is a sequence of one or more attributes associated with an entity. Attributes may be any of a variety of different types, e.g., integer, float, Boolean, string, etc. The attributes may be ordered. In addition to attributes associated with an entity, a tuple may include metadata, i.e., data about the tuple. A tuple may be extended by adding one or more additional attributes or metadata to it. As used herein, “stream” or “data stream” refers to a sequence of tuples. Generally, a stream may be considered a pseudo-infinite sequence of tuples.
Tuples are received and output by stream operators and processing elements. An input tuple corresponding with a particular entity that is received by a stream operator or processing element, however, is generally not considered to be the same tuple that is output by the stream operator or processing element, even if the output tuple corresponds with the same entity or data as the input tuple. An output tuple need not be changed in some way from the input tuple.
Nonetheless, an output tuple may be changed in some way by a stream operator or processing element. For stream operators, a tuple may be changed according to port mutability conditions. Port mutability is a characteristic of a stream operator and applies to tuples processed or submitted by the stream operator. The mutability of input ports indicate the intent of the stream operator logic to change incoming tuples. The mutability of the stream output ports indicate whether the stream operator grants permission for submitted tuples to be modified by downstream operators. For example, a mutable input port indicates that a stream operator intends to modify the tuples received at the port while an immutable input port indicates that the stream operator is only going to read, and not modify, the received tuple.
Attribute mutability/immutability may depend on both the tuple type definition and/or tuple processing logic. Each tuple attribute may have a corresponding attribute mutability condition that defines whether a stream operator receiving the tuple intends to modify the attribute. An attribute that will not be modified by the receiving stream operator is considered immutable, while an attribute that will be modified by the receiving stream operator is considered mutable. An attribute or metadata from a tuple may be added, deleted, or modified. For example, a tuple will often have two or more attributes. A stream operator or processing element may receive the tuple having multiple attributes and output a tuple corresponding with the input tuple. The stream operator or processing element may only change one of the attributes so that all of the attributes of the output tuple except one are the same as the attributes of the input tuple.
Generally, a particular tuple output by a stream operator or processing element may not be considered to be the same tuple as a corresponding input tuple even if the input tuple is not changed by the processing element. However, to simplify the present description and the claims, an output tuple that has the same data attributes or is associated with the same entity as a corresponding input tuple will be referred to herein as the same tuple unless the context or an express statement indicates otherwise.
Stream computing applications handle massive volumes of data that need to be processed efficiently and in real time. For example, a stream computing application may continuously ingest and analyze hundreds of thousands of messages per second and up to petabytes of data per day. Accordingly, each stream operator in a stream computing application may be required to process a received tuple within fractions of a second. Unless the stream operators are located in the same processing element, it is necessary to use an inter-process communication path each time a tuple is sent from one stream operator to another. Inter-process communication paths can be a critical resource in a stream computing application. According to various embodiments, the available bandwidth on one or more inter-process communication paths may be conserved. Efficient use of inter-process communication bandwidth can speed up processing.
An operator graph can be an execution path for a plurality of stream operators to process a stream of tuples. In addition to stream operators, the operator graph can refer to an execution path for processing elements and the dependent stream operators of the processing elements to process the stream of tuples. Generally, the operator graph can have a plurality of stream operators that produce a particular end result, e.g., calculate an average. An operator graph may be a linear arrangement of processing elements and/or operators, or it may include one or more distinct execution paths, also known as sub-processes, methods, or branches.
As tuples are passed between stream operators, there are two common scenarios. A stream operator may either read or read and modify tuples. For example, when downstream stream operators only need to read the tuple, a tuple reference may be used and multiple operators may use the same reference. Conversely, for example, when downstream stream operators need to both read and modify the tuple, a tuple copy may be used and multiple operators may receive their own copy of the tuple. In the second example (e.g., when tuple copying is used), multiple copies of a tuple are made even though less than all attributes of the tuple may be utilized downstream. For instance, a filter stream operator may access only a single tuple attribute (e.g., a stock ticker symbol) prior to discarding the tuple. This leads to multiple copy requests that are never needed. Additionally, creating multiple copies of a tuple may influence how programs are written. For example, instead of copying an entire text file into memory such that a downstream stream operator can access the file from memory, a file pointer is used and each downstream stream operator is required to read the file from disk prior to computation, resulting in compounding performance issues.
The communications network 120 may include a variety of types of physical communication channels or “links.” The links may be wired, wireless, optical, or any other suitable media. In addition, the communications network 120 may include a variety of network hardware and software for performing routing, switching, and other functions, such as routers, switches, or bridges. The communications network 120 may be dedicated for use by a stream computing application or shared with other applications and users. The communications network 120 may be any size. For example, the communications network 120 may include a single local area network or a wide area network spanning a large geographical area, such as the Internet. The links may provide different levels of bandwidth or capacity to transfer data at a particular rate. The bandwidth that a particular link provides may vary depending on a variety of factors, including the type of communication media and whether particular network hardware or software is functioning correctly or at full capacity. In addition, the bandwidth that a particular link provides to a stream computing application may vary if the link is shared with other applications and users. The available bandwidth may vary depending on the load placed on the link by the other applications and users. The bandwidth that a particular link provides may also vary depending on a temporal factor, such as time of day, day of week, day of month, or season.
Each CPU 205 retrieves and executes programming instructions stored in the memory 225 or storage 230. Similarly, the CPU 205 stores and retrieves application data residing in the memory 225. The interconnect 220 is used to transmit programming instructions and application data between each CPU 205, I/O device interface 210, storage 230, network interface 215, and memory 225. The interconnect 220 may be one or more busses. The CPUs 205 may be a single CPU, multiple CPUs, or a single CPU having multiple processing cores in various embodiments. In one embodiment, a processor 205 may be a digital signal processor (DSP). One or more processing elements 235 (described below) may be stored in the memory 225. A processing element 235 may include one or more stream operators 240 (described below). In one embodiment, a processing element 235 is assigned to be executed by only one CPU 205, although in other embodiments the stream operators 240 of a processing element 235 may include one or more threads that are executed on two or more CPUs 205. The memory 225 is generally included to be representative of a random access memory, e.g., Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), or Flash. The storage 230 is generally included to be representative of a non-volatile memory, such as a hard disk drive, solid state device (SSD), or removable memory cards, optical storage, flash memory devices, network attached storage (NAS), or connections to storage area network (SAN) devices, or other devices that may store non-volatile data. The network interface 215 is configured to transmit data via the communications network 120.
A stream computing application may include one or more stream operators 240 that may be compiled into a “processing element” container 235. Two or more processing elements 235 may run on the same memory 225, each processing element having one or more stream operators 240. Each stream operator 240 may include a portion of code that processes tuples flowing into a processing element and outputs tuples to other stream operators 240 in the same processing element, in other processing elements, or in both the same and other processing elements in a stream computing application. Processing elements 235 may pass tuples to other processing elements that are on the same compute node 110 or on other compute nodes that are accessible via communications network 120. For example, a processing element 235 on compute node 110A may output tuples to a processing element 235 on compute node 110B.
The storage 230 may include a buffer 260. Although shown as being in storage, the buffer 260 may be located in the memory 225 of the compute node 110 or in a combination of both memories. Moreover, storage 230 may include storage space that is external to the compute node 110, such as in a cloud.
The compute node 110 may include one or more operating systems 262. An operating system 262 may be stored partially in memory 225 and partially in storage 230. Alternatively, an operating system may be stored entirely in memory 225 or entirely in storage 230. The operating system provides an interface between various hardware resources, including the CPU 205, and processing elements and other components of the stream computing application. In addition, an operating system provides common services for application programs, such as providing a time function.
Each CPU 305 retrieves and executes programming instructions stored in the memory 325 or storage 330. Similarly, each CPU 305 stores and retrieves application data residing in the memory 325 or storage 330. The interconnect 320 is used to move data, such as programming instructions and application data, between the CPU 305, I/O device interface 310, storage unit 330, network interface 315, and memory 325. The interconnect 320 may be one or more busses. The CPUs 305 may be a single CPU, multiple CPUs, or a single CPU having multiple processing cores in various embodiments. In one embodiment, a processor 305 may be a DSP. Memory 325 is generally included to be representative of a random access memory, e.g., SRAM, DRAM, or Flash. The storage 330 is generally included to be representative of a non-volatile memory, such as a hard disk drive, solid state device (SSD), removable memory cards, optical storage, Flash memory devices, network attached storage (NAS), connections to storage area-network (SAN) devices, or the cloud. The network interface 315 is configured to transmit data via the communications network 120.
The memory 325 may store a stream manager 134. Additionally, the storage 330 may store an operator graph 132. The operator graph 132 may define how tuples are routed to processing elements 235 (
The management system 105 may include one or more operating systems 332. An operating system 332 may be stored partially in memory 325 and partially in storage 330. Alternatively, an operating system may be stored entirely in memory 325 or entirely in storage 330. The operating system provides an interface between various hardware resources, including the CPU 305, and processing elements and other components of the stream computing application. In addition, an operating system provides common services for application programs, such as providing a time function.
Each CPU 405 retrieves and executes programming instructions stored in the memory 425 or storage 430. Similarly, each CPU 405 stores and retrieves application data residing in the memory 425 or storage 430. The interconnect 420 is used to move data, such as programming instructions and application data, between the CPU 405, I/O device interface 410, storage unit 430, network interface 415, and memory 425. The interconnect 420 may be one or more busses. The CPUs 405 may be a single CPU, multiple CPUs, or a single CPU having multiple processing cores in various embodiments. In one embodiment, a processor 405 may be a DSP. Memory 425 is generally included to be representative of a random access memory, e.g., SRAM, DRAM, or Flash. The storage 430 is generally included to be representative of a non-volatile memory, such as a hard disk drive, solid state device (SSD), removable memory cards, optical storage, flash memory devices, network attached storage (NAS), connections to storage area-network (SAN) devices, or to the cloud. The network interface 415 is configured to transmit data via the communications network 120.
The development system 102 may include one or more operating systems 432. An operating system 432 may be stored partially in memory 425 and partially in storage 430. Alternatively, an operating system may be stored entirely in memory 425 or entirely in storage 430. The operating system provides an interface between various hardware resources, including the CPU 405, and processing elements and other components of the stream computing application. In addition, an operating system provides common services for application programs, such as providing a time function.
The memory 425 may store a compiler 136. The compiler 136 compiles modules, which include source code or statements, into the object code, which includes machine instructions that execute on a processor. In one embodiment, the compiler 136 may translate the modules into an intermediate form before translating the intermediate form into object code. The compiler 136 may output a set of deployable artifacts that may include a set of processing elements and an application description language file (ADL file), which is a configuration file that describes the stream computing application. In some embodiments, the compiler 136 may be a just-in-time compiler that executes as part of an interpreter. In other embodiments, the compiler 136 may be an optimizing compiler. In various embodiments, the compiler 136 may perform peephole optimizations, local optimizations, loop optimizations, inter-procedural or whole-program optimizations, machine code optimizations, or any other optimizations that reduce the amount of time required to execute the object code, to reduce the amount of memory required to execute the object code, or both. The output of the compiler 136 may be represented by an operator graph, e.g., the operator graph 132 of
The compiler 136 may also provide the application administrator with the ability to optimize performance through profile-driven fusion optimization. Fusing operators may improve performance by reducing the number of calls to a transport. While fusing stream operators may provide faster communication between operators than is available using inter-process communication techniques, any decision to fuse operators requires balancing the benefits of distributing processing across multiple compute nodes with the benefit of faster inter-operator communications. The compiler 136 may automate the fusion process to determine how to best fuse the operators to be hosted by one or more processing elements, while respecting user-specified constraints. This may be a two-step process, including compiling the application in a profiling mode and running the application, then re-compiling and using the optimizer during this subsequent compilation. The end result may, however, be a compiler-supplied deployable application with an optimized application configuration.
The example operator graph shown in
The operator graph 500 begins at a source 502 and ends at a sink 504, 506. Compute node 110A includes the processing elements PE1, PE2, and PE3. Source 502 flows into the processing element PE1, which in turn outputs tuples that are received by PE2 and PE3. For example, PE1 may split data attributes received in a tuple and pass some data attributes in a new tuple to PE2, while passing other data attributes in another new tuple to PE3. As a second example, PE1 may pass some received tuples to PE2 while passing other tuples to PE3. Tuples that flow to PE2 are processed by the stream operators contained in PE2, and the resulting tuples are then output to PE4 on compute node 110B. Likewise, the tuples output by PE4 flow to PE6 before being transmitted to a sink 504. Similarly, tuples flowing from PE3 to PE5 also reach PE6 and are sent to a sink 504. Thus, PE6 could be configured to perform a join operation, combining tuples received from PE4 and PE5, before sending the data to the sink 504. This example operator graph also shows tuples flowing from PE3 to PE7 on compute node 110C, which itself shows tuples flowing to PE8 and looping back to PE7. Tuples output from PE8 flow to PE9 on compute node 110D, which in turn outputs tuples to be processed by operators in PE10 before being sent to a sink 506.
The tuple received by a particular processing element 235 (
Processing elements 235 (
The stream manager 134 of
Because a processing element may be a collection of fused stream operators, it is equally correct to describe the operator graph as one or more execution paths between specific stream operators, which may include execution paths to different stream operators within the same processing element.
The tuple 616 comprises an attribute X 618A and an attribute Y 620 whereas the tuple 617 comprises an attribute X copy 618B and an attribute reference 622.
The stream operators 602-606 included in the operator graph 600 may be part of a single processing element. In embodiments, the stream operators 602-606 may each belong to separate processing elements. In further embodiments, the stream operators 602-606 may each occupy their own individual memory space. However, in an embodiment where the stream operators 602-606 do not share memory space with one another, they may require access to the memory space occupied by each individual stream operator.
The output ports A 608 and C 612, and input ports B 610 and D 614, may interact with streams 609 and 613 entering and/or leaving stream operators 602-606. Specifically, output port A 608 transmits stream 609 from the stream operator 602 to the input port B 610 of the stream operator 604. Similarly, output port C 612 transmits stream 613 from the stream operator 604 to the input port D 614 of the stream operator 606.
The tuple 616 is part of the stream 609 leaving the output port A 608 from the stream operator 602 going to the input port B 610 of the stream operator 604. In embodiments, the tuple 616 may comprise a plurality of attributes. The tuple 617 is part of the stream 613 leaving the output port C 612 from the stream operator 604 going to the input port D 614 of the stream operator 606. The attribute X copy 618B is a copy of the attribute X 618A from the tuple 616. For example, the attribute X copy 618B may be made at the input port B 610 of the stream operator 604. In various embodiments, a copy of an attribute may include all of the data/metadata comprising the attribute. The attribute reference 622 is a reference to the attribute Y 620 from the tuple 616. In embodiments, the attribute reference 622 may be a file pointer inserted into the place of an attribute within a tuple, where the file pointer directs a downstream stream operator to access and read the file associated with the attribute from disk memory (e.g., shared/unshared memory) prior to computations. For example, the attribute reference 622 may direct the input port D 614 of the stream operator 606 to the attribute Y 620 of the tuple 616, which may be saved and/or stored in the memory space of the stream operator 602.
Attribute copying within the example operator graph 600 may be dependent upon the port mutability conditions for the stream operators 602-606. In some embodiments, attribute copying within the example operator graph 600 may be dependent upon the attribute mutability conditions for attribute X 618A and attribute Y 620 from tuple 616 and attribute X copy 618B and attribute reference 622 from tuple 617. In some embodiments, the port mutability conditions for the stream operators 602-606 may be determined from the logic that is applied to each stream (e.g., streams 609 and 613) passing through the input and/or output ports associated with the stream operators 602-606. When an input port is configured to be mutable, the stream operator intends to modify tuples received at the input port. Conversely, when an input port is configured to be immutable, the stream operator intends to only read the tuples received at the input port. Similarly, when an output port is configured to be mutable, the stream operator containing that output port allows the modification of the submitted tuple (e.g., the tuple leaving the operator) by a downstream stream operator. Further, when an output port is configured to be immutable, the stream operator intends to only read the tuples received. For operators within a processing element, the port mutability conditions may be explicitly defined. For example, products such as InfoSphere® Streams (InfoSphere is a registered trademark of International Business Machines Corporation of Armonk, N.Y) specify port mutability conditions as stream operator metadata in a separate stream operator model file.
Attribute mutability conditions for the attributes X 618A, Y 620 and X copy 618B may be determined from and/or based on the logic that is applied to each attribute within a tuple. In embodiments, attribute mutability conditions may depend on the tuple type definition and/or the tuple processing logic. The tuple type definition is a classification identifying one of the various types of data for each attribute, such as real, integer or Boolean, that determines the possible values for that type, the operations that can be done on the values of that type, the meaning of the data, and/or the way values of that type can be stored. The tuple processing logic is the code/program that reads or modifies a tuple (e.g., a stream operator). In various embodiments, attribute mutability conditions may be inferred from the tuple processing logic. In certain embodiments, similar to port mutability conditions, attribute mutability conditions may be explicitly declared.
In the operator graph 600, a stream containing a plurality of tuples may enter the stream operator 602 through an input port not shown. The port mutability conditions may be determined before any tuple processing occurs. In embodiments, the port mutability conditions may be determined while tuple processing occurs. Thus, for example, it may be determined that the output port A 608 for the stream operator 602 is immutable and the input port B 610 for the stream operator 604 is mutable. Accordingly, tuple copying will occur because the stream operator 604 intends to modify the tuple 616 (e.g., received the tuple 616 at the mutable input port B 610) and the stream operator 602 is configured to disallow modification of the tuple 616 (e.g., it transmitted the tuple 616 from the immutable output port A 608).
The attribute mutability conditions for the attributes X 618A and Y 620 of the tuple 616 may be inferred by the data streaming language compiler if it understands the tuple processing logic. For example as shown in Table 1, in the data flow fragment written in a Streams Processing Language (e.g., a distributed data flow composition language that is used in InfoSphere® Streams), the streaming language compiler can infer that only the attribute X 618A needs to be copied:
The attribute mutability conditions for the attributes X 618A and Y 620 of the tuple 616 may be explicitly specified when the data streaming language compiler does not have visibility into the operator logic. For example, Table 2 is a data flow fragment written in SPL where the stream operator 602 is connected to a primitive stream operator (e.g., steam operator 604). The SPL compiler does not have access to the tuple processing logic implemented by the primitive operator, therefore attribute mutability conditions may be explicitly declared using the “const” keyword:
Once the port mutability conditions for the stream operators 602-606 are determined as well as the attribute mutability conditions for the tuple 616 and the attribute mutability conditions for the tuple 617, the streams 609 and 613 may be processed through the operator graph 600. For the examples above, the compiler determined that the stream operator 604 only changes the attribute X 618A, so the stream operator 604 makes a copy of the attribute X 618A and places a reference to the attribute Y 620 from the tuple 616 into the attribute reference 622 within the tuple 617. The input port D 614 of the stream operator 606 is immutable, and therefore it receives a reference to the attribute Y 620 in the tuple 617 as the attribute reference 622. In embodiments, the stream operator 606 logic may write the data from the tuple 617 to a file. When the stream operator 606 retrieves the attribute reference 622, data from the attribute Y 620 in the tuple 616 may be referenced utilizing stream operator software (e.g., an attribute getter function) without having to make an intermediate copy of the attribute Y 620.
Using the port mutability conditions for the stream operators 602-606 and the attribute mutability conditions for the tuple 616, the operator graph 600 avoids copying attribute Y 620. In embodiments, the tuple data structure of the operator graph 600 may be able to store a reference to the attribute of another tuple (e.g., attribute Y 620). In various embodiments, reference counting may be enabled within the operator graph 600. Reference counting may avoid removing from memory a tuple (e.g., tuple 616) as long as at least one attribute of the tuple is referenced by another tuple (e.g., tuple 617).
The stream operators 702-710 included in the operator graph 700 may be part of a single processing element. In embodiments, the stream operators 702-710 may each belong to separate processing elements. In further embodiments, the stream operators 702-710 may each occupy their own individual memory space. However, in an embodiment where the stream operators 702-710 do not share memory space with one another, they may require access to the memory space occupied by each individual stream operator.
The output ports A 712, C1718, C 720, and input ports B1714, B 716, D1722, D 724, may interact with streams 726, 728, 730 and 732 entering and/or leaving stream operators 702-710. Specifically, output port A 712 transmits streams 726 and 728 from the stream operator 702 to the input ports B1714 and B 716 of the stream operators 704 and 706, respectfully. Stream 726 leaving the output port A 712 from the stream operator 702 fans out to create the stream 728. In embodiments, the stream 726 and the stream 728 may comprise the same tuples. In various embodiments, to fan out defines the number of input ports a stream leaving an output port may feed or connect to. For example, the stream 726 fans out more than once (e.g., twice) because it is connected to the input ports B1714 and B 716 of the stream operators 704 and 706, respectively. Additionally, output ports C1718 and C 720 transmit streams 730 and 732 from the stream operators 704 and 706 to the input ports D1722 and D 724 of the stream operators 708 and 710, respectively.
The tuple 734 is part of the stream 726 and/or 728 leaving the output port A 712 from the stream operator 702 going to the input ports B1714 and B 716 of the stream operators 704 and 706, respectively. In embodiments, the tuple 734 may comprise a plurality of attributes. The tuple 735 is part of the stream 730 leaving the output port C1718 from the stream operator 704 going to the input port D1722 of the stream operator 708. The attribute X copy 736B is a copy of the attribute X 736A from the tuple 734. For example, the attribute X copy 736B may be made at the input port B1 of the stream operator 704. In various embodiments, a copy of an attribute may include all of the data/metadata comprising the attribute. The attribute reference 740 is a reference to the attribute Y 738 from the tuple 734. In embodiments, the attribute reference 740 may be a file pointer inserted into the place of an attribute within a tuple, where the file pointer directs a downstream stream operator to access and read the file associated with the attribute from disk memory (e.g., shared/unshared memory) prior to computations. For example, the attribute reference 740 may direct the input port D1 of the stream operator 708 to the attribute Y 738 of the tuple 734, which may be saved and/or stored in the memory space of the stream operator 702.
Attribute copying within the example operator graph 700 may be dependent upon the port mutability conditions for the stream operators 702-710. In some embodiments, attribute copying within the example operator graph 700 may be dependent upon the attribute mutability conditions for attribute X 736A and attribute Y 738 from tuple 734 and attribute X copy 736B and attribute reference 740 from tuple 735. In certain embodiments, the port mutability conditions for the stream operators 702-710 may be determined from the logic that is applied to each stream (e.g., streams 726, 728, 730 and 732) passing through the input and/or output ports associated with the stream operators 702-710.
Attribute mutability conditions for the attributes X 736A, Y 738 and X copy 736B may be determined from and/or based on the logic that is applied to each attribute within a tuple. In embodiments, attribute mutability conditions may depend on the tuple type definition and/or the tuple processing logic. In various embodiments, attribute mutability conditions may be inferred from the tuple processing logic. In certain embodiments, similar to port mutability conditions, attribute mutability conditions may be explicitly declared.
In the operator graph 700, a stream containing a plurality of tuples may enter the stream operator 702 through an input port not shown. The port mutability conditions may be determined before any tuple processing occurs. In embodiments, the port mutability conditions may be determined while tuple processing occurs. Thus, for example, it may be determined that the output port A 712 for the stream operator 702 is mutable, the input port B1714 for the stream operator 704 is mutable, and the input port D1722 is immutable. In embodiments, the input port B 716 may be mutable. In various embodiments, the input port B 716 may be immutable. Accordingly, tuple copying will occur because the output port A 712 of the stream operator 702 is mutable (e.g., allows modification of the submitted tuple 734 by downstream operators), the stream 726 leaving the output port A 712 is received by at least two downstream operators (e.g., stream operators 704 and 706), and one of the two downstream operators contains a mutable input port (e.g., the mutable input port B1714 will modify the received tuple 734).
The attribute mutability conditions for the attributes X 736A and Y 738 of the tuple 734 may be inferred by the data streaming language compiler if it understands the tuple processing logic. For example, similar to the discussion associated with Table 1 in
Once the port mutability conditions for the stream operators 702-710 are determined as well as the attribute mutability conditions for the tuple 734 and the attribute mutability conditions for the tuple 735, the streams 726, 728, 730 and 732 may be processed through the operator graph 700. For the examples above, the compiler may have determined that the stream operator 704 only changes the attribute X 736A, so the stream operator 704 makes a copy of the attribute X 736A and places a reference to the attribute Y 738 from the tuple 734 into the attribute reference 740 within the tuple 735. The input port D1722 of the stream operator 708 is immutable, and therefore it receives a reference to the attribute Y 738 in the tuple 735 as the attribute reference 740. In embodiments, the stream operator 708 logic may write the data from the tuple 735 to a file. When the stream operator 708 retrieves the attribute reference 740, data from the attribute Y 738 in the tuple 734 may be referenced utilizing stream operator software (e.g., an attribute getter function) without having to make an intermediate copy of the attribute Y 738.
Using the port mutability conditions for the stream operators 702-710 and the attribute mutability conditions for the tuple 734, the operator graph 700 avoids copying attribute Y 738. In embodiments, the tuple data structure of the operator graph 700 may be able to store a reference to the attribute of another tuple (e.g., attribute Y 738). In various embodiments, reference counting may be enabled within the operator graph 700. Reference counting may avoid removing from memory a tuple (e.g., tuple 734) as long as at least one attribute of the tuple is referenced by another tuple (e.g., tuple 735).
The first stream operator may include a plurality of input and/or output ports. For example, the first stream operator may be able to process a plurality of streams received by the plurality of input ports and may generate a plurality of outgoing streams leaving the plurality of output ports. The first stream operator is connected to at least one additional stream operator (e.g., a second stream operator discussed herein). In embodiments, the first stream operator may be connected to a plurality of stream operators. Connecting the first stream operator with additional stream operators may include fanning out streams leaving the first stream operator. For example, a singular stream leaving the first stream operator through an output port may connect to two additional stream operators, such as a second stream operator and a third stream operator.
At block 804, the port mutability conditions are determined. In embodiments, determining the port mutability conditions includes analyzing each input/output ports for each operator utilizing the process 800. Analyzing the port mutability conditions may include identifying operators where multiple copies of a tuple will be made. The port mutability conditions may be explicitly defined. For example, products such as InfoSphere® Streams specify port mutability conditions as stream operator metadata in a separate stream operator model file.
At block 806, the process 800 determines whether or not attribute copying is required for a first tuple passing through a first stream operator. Determining whether attribute copying is required may be based upon the attribute mutability conditions for the first tuple passing through the first stream operator and the port mutability conditions for at least two stream operators. For example, when an output port for a first stream operator is immutable and when an input port for a second stream operator is mutable, tuple copying will occur. In another example, when an output port for a stream operator is mutable, the stream leaving the output port of the stream operator is received by at least two additional stream operators, and one of the two additional stream operators has a mutable input port (e.g., a second stream operator with a mutable input port), tuple copying will occur. In some embodiments, aspects of the process 800 may be similar or the same as aspects described in
At block 808, in response to determining that at least one attribute does not need to be copied, a reference is created for each attribute that does not need to be copied. The reference identifies where in the first tuple the information is stored. In embodiments, a plurality of references may be created. In various embodiments, the tuple data structure of the tuple passing through the first stream operator may be able to store the reference to the attribute of another tuple. Creating a reference may include replacing the unmodified attribute of the tuple passing through the first stream operator with a file pointer. In embodiments, replacing the unmodified attribute of the tuple passing through the first stream operator with a file pointer may include writing the tuple data of the first tuple to a file (e.g., shared memory space). In certain embodiments, creating a reference may include enabling reference counting to avoid deleting from memory the first tuple while one or more of its attributes are referenced by other tuples.
At block 810, a second tuple is generated by the first stream operator and transmitted through an output port to a downstream operator. In some embodiments, generating a second tuple includes applying the logic of the first stream operator to the first tuple. In certain embodiments, generating a second tuple may include replacing unmodified attributes of the first tuple with references created at block 808. In embodiments, the second tuple may include attributes from the first tuple, copies of attributes from the first tuple, and/or references. In various embodiments, the second tuple may be comprised entirely of references.
At block 812, the process 800 determines whether or not attribute copying is required for the second tuple passing through a second stream operator. In embodiments, determining whether or not attribute copying is required for the second tuple passing through a second stream operator may be similar or the same as that described at block 806. Determining whether attribute copying is required may be based upon the attribute mutability conditions for the second tuple passing through the first stream operator and the port mutability conditions for at least the first stream operator and the second stream operator. In certain embodiments, aspects of the process 800 may be similar or the same as aspects described in
At block 814, in response to determining that at least one attribute does not need to be copied for the second tuple, a reference is created for each attribute that does not to be copied, the reference identifying where in the second tuple the information is stored. In embodiments, a plurality of references may be created. In various embodiments, the tuple data structure of the tuple passing through the first stream operator may be able to store the reference to the attribute of another tuple. Creating a reference may include replacing the unmodified attribute of the tuple passing through the second stream operator with a file pointer. In embodiments, replacing the unmodified attribute of the tuple passing through the second stream operator with a file pointer may include writing the tuple data of the second tuple to a file (e.g., shared memory space). In certain embodiments, creating a reference may include enabling reference counting to avoid deleting from memory the first tuple and/or second tuple while one or more of its attributes are referenced by other tuples.
At block 816, a third tuple is generated from the output port of the second stream operator. In embodiments, generating a third tuple may include applying the logic of the second stream operator to the second tuple. In certain embodiments, generating a third tuple may include replacing unmodified attributes of the second tuple with references created at block 814. In embodiments, the third tuple may include attributes from the first tuple, copies of attributes from the first tuple, attributes from the second tuple, and/or references. In various embodiments, the second tuple may be comprised entirely of references.
As discussed in more detail herein, it is contemplated that some or all of the operations of some of the embodiments of methods described herein may be performed in alternative orders or may not be performed at all; furthermore, multiple operations may occur at the same time or as an internal part of a larger process.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the various embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “includes” and/or “including,” when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. In the previous detailed description of exemplary embodiments of the various embodiments, reference was made to the accompanying drawings (where like numbers represent like elements), which form a part hereof, and in which is shown by way of illustration specific exemplary embodiments in which the various embodiments may be practiced. These embodiments were described in sufficient detail to enable those skilled in the art to practice the embodiments, but other embodiments may be used and logical, mechanical, electrical, and other changes may be made without departing from the scope of the various embodiments. In the previous description, numerous specific details were set forth to provide a thorough understanding the various embodiments. But, the various embodiments may be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not to obscure embodiments.
Different instances of the word “embodiment” as used within this specification do not necessarily refer to the same embodiment, but they may. Any data and data structures illustrated or described herein are examples only, and in other embodiments, different amounts of data, types of data, fields, numbers and types of fields, field names, numbers and types of rows, records, entries, or organizations of data may be used. In addition, any data may be combined with logic, so that a separate data structure may not be necessary. The previous detailed description is, therefore, not to be taken in a limiting sense.
The descriptions of the various embodiments of the present disclosure have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Although the present invention has been described in terms of specific embodiments, it is anticipated that alterations and modification thereof will become apparent to the skilled in the art. Therefore, it is intended that the following claims be interpreted as covering all such alterations and modifications as fall within the true spirit and scope of the invention.
The descriptions of the various embodiments of the present disclosure have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
