NZ616212B - System and method for batch evaluation programs - Google Patents

System and method for batch evaluation programs

Info

Publication number
NZ616212B
NZ616212B NZ616212A NZ61621213A NZ616212B NZ 616212 B NZ616212 B NZ 616212B NZ 616212 A NZ616212 A NZ 616212A NZ 61621213 A NZ61621213 A NZ 61621213A NZ 616212 B NZ616212 B NZ 616212B
Authority
NZ
New Zealand
Prior art keywords
expression
evaluated
batch
call stack
stack
Prior art date
Application number
NZ616212A
Other versions
NZ616212A (en
Inventor
E Marinelli Eugene Iii
Namara Yoga
Original Assignee
Palantir Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/657,635 external-priority patent/US9348677B2/en
Application filed by Palantir Technologies Inc filed Critical Palantir Technologies Inc
Publication of NZ616212A publication Critical patent/NZ616212A/en
Publication of NZ616212B publication Critical patent/NZ616212B/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/48Indexing scheme relating to G06F9/48
    • G06F2209/484Precedence
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services

Abstract

computer-implemented method and a computer system for batch evaluate a plurality of expressions are disclosed. The computer system comprises a memory; and a processor. The processor is configured to analyse a first expression to be evaluated within a first call stack (202) associated with a first instruction of a software routine with the first instruction specifying the first expression; determine that the first expression and a second expression to be evaluated within a different call stack (202) should be batch evaluated, cause the first expression and the second expression to be evaluated; receive a different value for each of the first expression and the second expression that is generated when the batch processing request is processed by the application server, and populate the first call stack (202) with the value for the first expression. The different call stack (202) is associated with a second instruction of the software routine and the second instruction specifies the second expression. t instruction of a software routine with the first instruction specifying the first expression; determine that the first expression and a second expression to be evaluated within a different call stack (202) should be batch evaluated, cause the first expression and the second expression to be evaluated; receive a different value for each of the first expression and the second expression that is generated when the batch processing request is processed by the application server, and populate the first call stack (202) with the value for the first expression. The different call stack (202) is associated with a second instruction of the software routine and the second instruction specifies the second expression.

Description

SYSTEM AND METHOD FOR BATCH TION PROGRAMS Technical Field The present disclosure relates generally to data access and analysis and, more specifically, to a system and method for evaluating programs in batch.
Background Software applications, such as financial analysis applications, allow users to create and interact with large software data s. Such data objects organize data relevant to the re application and provide methods that allow operations to be performed on the data. in some situations, the operations are performed on a large set of data and require high processing power as well as high dth access to a database.
Typically, for the ent processing of such operations, the bulk of the processing occurs on a server that is external to the computing device that executes the software application. ln operation, the software application transmits calls associated with the operations to be performed on the data, and the calls are processed on the server. The results of the processing are then transmitted back to the software application for presentation to the user.
One drawback to such an implementation is that the server receives and processes one call per operation to be performed. In ions where operations are performed on an extremely large set of data, serving a large amount of calls can slow down the server and, in some cases, crash the server.
Such a io is extremely undesirable e the server is extremely slow and in some cases entirely unusable, thereby affecting the overall user expenence.
As the foregoing illustrates, what is needed in the art is a mechanism for efficiently managing and processing a large volume of calls to be processed on a server. 7890071_1 Summary One aspect of the present disclosure provides a computer—implemented method to facilitate batch evaluation of a plurality of expressions, the method comprising: analyzing a first expression to be evaluated within a first call stack associated with a first instruction of a software routine, n the first ction specifies the first expression; determining whether the first expression and a second expression to be ted within a different call stack should be batch evaluated; expression in a stack evaluator; in response to determiningthat the first sion and the second expression should be batch evaluated, causing the first expression and the second expression to be evaluated in an application server; receiving, from the application server, a different value for each of the first expression and the second expression that is generated when a batch processing request is processed by the application server; and populating the first call stack with the ed value for the first sion.
Advantageously, e a single batch processing request is transmitted to the application server for a group of similar expressions, the number of processing requests received by the application server is reduced. As a result, the application server is not burdened with a large amount of requests at any given time. Therefore, the overall processing efficiency of the application server is increased and the overall processing latency of the application server is reduced.
Brief Description of the Figures 80 that the manner in which the above recited es of the t invention can ‘ be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended gs. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
Figure 1 illustrates a system that enables an application to be processed in batch- mode, according to one embodiment of the invention; Figure 2A illustrates a more detailed view of the stack tor of Figure 1, ing to one ment of the invention; 9525423 Figure 2B rates a more detailed view of the stack of Figure 2A, according to one embodiment of the invention; Figure 3 rates a more detailed view of the batching module of Figure 1, according to one embodiment of the invention; Figure 4 is an exemplary system within which the ation of Figure 1 could execute, ing to one embodiment of the invention; Figures 5A and SB set forth a flow diagram of method steps for evaluating a program instruction within the stack evaluator, according to one embodiment of the invention; and Figures 6A and 6B set forth a flow m of method steps for processing related program instructions in batches, according to one embodiment of the invention.
Detailed ption Figure 1 illustrates a system 100 that enables an application to be processed in batch-mode. As shown, the system 100 includes a application 102, service logic 104, an application server 106 and a data store 108.
The application 102 is a software program that allows a user to create, analyze and interact with workflows having one or more documents. A document is typically ed of several data objects, each having a particular type and function. The data objects that could make up a document are described in r detail below. A user, via a programming interface, can typically write program routines that interact with the data objects to generate the results or analysis needed. Again, some examples of such instructions are described below.
The service logic 104 is an infrastructure layer that, among other things, allows the application 102 to communicate with the application server 106. ln one embodiment, the service logic 104 includes a ing service (not shown) that allows the application 102 and the application server 106 to communicate asynchronously via messages. The service logic 104 includes a 7890071_1 stack evaluator 118 and a batching module 120. The stack evaluator 118 is an infrastructure module that manages the stack-based evaluation of program routines associated with the application 102. Each program routine is associated with a call stack that includes multiple frames, each frame storing information about a ular portion of the program routine. The batching module 120 allows for the batch processing on the application server 106 of program routines being evaluated within the stack evaluator 118. The functions of the stack evaluator 118 and the batching module 120 is described in greater detail below in conjunction with s 2A-BB.
The application server 106 es logical elements such as input ing logic 110, an object model 112, evaluation logic 114 and data store access logic 116. The application server 106 may be implemented as a special—purpose er system having the logical elements shown in Figure 1. in one embodiment, the logical elements se program instructions stored on one or more machine—readable storage media. atively, the logical elements may be implemented in hardware, firmware, or a combination thereof.
- The input receiving logic 110 receives inputs from different applications executing within the system 100, such as the application 102, via the service logic 104. Inputs include, but are not limited to, processing requests, data access/storage requests and expression evaluation requests.
The input receiving logic 110 transmits ts received from the different applications to l elements within the application server 106 that are configured to process those requests.
The object model 112 is a model that specifies a universe of data objects, relationships n the data objects, higher—order data objects generated based on one or more zero-order data objects in the universe, higher-order data objects generated based on other -order data objects, and auxiliary entities related to the universe of data objects. The data objects may be created by users via data object on mechanisms exposed in different applications, such as the application 102. In one embodiment, the object model 112 includes only references to the data objects and data related 7890071__1 to those data objects is stored within the data store 108. Persons skilled in the art would understand that any other data s can be included in the object model 112.
The evaluation logic 114 receives expression tion requests from applications, such as the application 102, via the input receiving logic and tes the expressions specifies in those requests. An expression typically includes a reference to one or more data objects included in the object model 112 and specifies one or more operations to be performed on those data s. The evaluation logic 114, when sing a particular expression, may create, modify, delete and store data s that are associated with the universe of data objects included in the object model 112. In addition, the evaluation logic 112 the evaluation logic 112 transmits the results of processing the particular sion to the application that transmitted the expression evaluation request.
In an embodiment, application server 106 comprises data store access logic 116. Data store access logic 116 may comprise a set of program instructions which, when ed by one or more processors, are operable to access and retrieve data from data store 108. For example, data store access logic 116 may be a se client or an Open Database Connectivity (ODBC) client that supports calls to a database server that manages data store 108.
Data store 108 may be any type of structured storage for storing data including, but not limited to, relational or object—oriented databases, data warehouses, directories, data files, and any other structured data storage.
Figure 2A illustrates a more detailed view of the stack evaluator 118 of Figure 1, according to one embodiment of the invention. As shown, the stack evaluator 118 es multiple stacks 202.
The stack evaluator 118 generates a stack 202 corresponding to each program subroutine (referred to herein as a “subroutine”) associated with the application 102. Typically, a subroutine es multiple instructions, where each instruction includes one or more expressions to be evaluated. As discussed above, an expression may include an argument, a parameter and/or 7890071_1 a metric, as described above. When evaluating a particular instruction, the stack evaluator 118 generates a different frame for each sion within that instruction. For example, an array frame is generated for each argument of an instruction and a call frame is generated for performing a specified operation on the arguments that were ted in the array frame(s).
Figure ZB illustrates a more detailed view of a stack 202 of Figure 2A, according to one embodiment of the invention. As shown, the stack 202 includes a frames portion 206, a value n 208 and an expression portion 210.
The frames portion 206 includes multiple frames 204, where each frame 204 corresponds to a particular evaluation iteration of the subroutine ponding to the stack 202. When a particular frame is ready for evaluation, the stack 202 transitions to an “evaluation ” During tion, the expressions within the current frame are first extracted and pushed into the expression array 210, such as exp 214. The value of the expressions are then evaluated and pushed into the value array 208. If an expression being ted is nested, the evaluation of the expression in the t frame 204 generates one or more new frames 204 that are evaluated before evaluating the current frame. Once the evaluation of each frame in the stack 202 is completed, the stack 202 transitions to a “completed state” Figure 3 illustrates a more detailed view of the batching module 120 of Figure 1, according to one embodiment of the invention. As shown, the batching module 120 includes an inspection engine 302, a blocking engine 304 and an unblocking engine.
The batching module 120 monitors the execution of program subroutines within the stack evaluator 118 to identify program subroutines that can be sed within the application server 106 in batch. More specifically, for each stack 202, the inspection engine 302 analyzes a current sion within a frame 204 of the stack 202 to determine whether the evaluation of the expression should be evaluated in batch with other similar expressions. 7890071_1 To determine whether a particular expression should be evaluated in batch with other similar expressions, the inspection engine 302 first determines the type of the sion. An expression may be an economic index, an instrument, a , an input object, an output object, a parameter, a time series, a —order-object, or any higher—order object in the object model.
Based on the type of expression, the inspection engine 302 then determines whether the type of the expression falls within a pre-determined category of expressions that should be processed in batch with other expressions of the same type or a similar type. For example, an expression that includes a metric for which the evaluation involves a database access or a model access should be processed in batch with other expressions that include s for which the evaluation involves database accesses or a model accesses.
As another example, consider the following program instruction: return lose + this.open, where “this” refers to a time series. There are multiple expressions within the program instruction, such as “this.close," “,"+ and “this.open,” In one scenario, the program instruction may be evaluated multiple times, each evaluation generating a different stack 202. In such a scenario, the inspection engine 302 may fy the expressions “this.close” and “this.open" as expressions that should be evaluated in batch with r expressions. Therefore, for each stack 202, the corresponding “this.close” expression is evaluated in batch with the “this.close” expressions in the remaining stacks 202. Similarly, for each stack 202, the corresponding “this.open” expression is evaluated in batch with the “this.open” expressions in the remaining stacks 202.
For a ular stack 202, once the inspection engine 302 determines that the current expression should be evaluated in batch with other similar expressions, the ng engine 304 blocks the processing of the t expression and the stack 202, in general. At this instant, the stack 202 transitions to a “blocked state.” Therefore, at any given point, a stack 202 is either in an evaluation state, a blocked state or a ted state. When all the stacks 202 are either in a blocked state or a completed state, the blocking engine 304 prepares the current expressions in each of the blocked stacks 202 7890071_1 (referred to herein as the “blocked sions”) for evaluation on the application server 106 in batch. The blocking engine 304 divides the blocked expressions into ions, where blocked expressions in a particular ion are each associated with at least one similar characteristic. For example, each blocked expression in a particular partition may need a database call to be executed by the application server 106.
Once the d expressions are divided into partitions, the blocking engine 304 dispatches, per partition, a single call to the application server 106 for evaluating all of the expressions in that partition. The application server 106 evaluates the expression in a manner described above in conjunction with Figure 1. The application server 106 transmits the results ated with each expression in a partition to the unblocking engine 306. For each result associated with a ular expression, the unblocking engine 306 updates the stack 202 ponding to the expression to store the result. The updated stack 202 is then unblocked and the frames 204 within the stack 202 continue to be processed.
The inspection engine 302 continues to inspect the stacks 202 to identify expressions that can be evaluated in batch. in turn, the blocking engine 304 continues to block stacks 202 and dispatch calls for evaluating r expressions in batch until each of the stacks 202 is in a completed state. In such a manner, similar expressions from different stacks 202 are processed in batch within the application server 106, thus increasing the efficiency of the overall system.
Figure 4 is an exemplary system within which the application 102 of Figure 1 could execute, according to one embodiment of the invention. As shown, the system 400 includes a system memory 402, an external memory 404, a central sing unit (CPU) 406, an input device 410 and an display device 412.
The system memory 402 includes the application 102 previously described herein. The system memory 402 is a memory space, usually a random access memory (RAM), that temporarily stores software programs 7890071_1 running within the system 400 at any given time. The CPU 406 executes a sequence of stored instructions associated with and/or transmitted from the various elements in the computer system 400. The external memory 404 is a storage device, eg. a hard disk, for storing data associated with the application 102. The input device 410 is an end-user controlled input device, eg. a mouse or keyboard, that allows a user to manipulate various aspects of the application 102. The display device 412 may be a cathode-ray tube (CRT), a liquid crystal display (LCD) or any other type of display device.
Figures 5A and SB set forth a flow diagram of method steps for ting a program instruction within the stack evaluator, according to one embodiment of the invention. Although the method steps are bed in conjunction with the system for Figure 1—4, persons skilled in the art will understand that any system configured to perform the method steps, in any order, is within the scope of the invention.
The method 500 begins at step 501, where the stack evaluator 118 generates a stack 202 corresponding to a program subroutine associated with the application 102 that is being evaluated. At step 502, the stack tor 118 tes a call frame associated with a particular program instruction included in the program subroutine. As discussed above, each program instruction within a m subroutine includes one or more expressions to be evaluated. An expression may be an argument, a parameter and/or a metric, as described above. Therefore, the call frame associated with the particular program instruction includes the one or more sions to be evaluated.
At step 504, the stack evaluator 118 generates a different child frame for evaluating each expression within that instruction. For example, an array frame is generated for each nt of an instruction. At step 506, the stack evaluator 118 transitions the stack 202 to an evaluation state. At step 508, the stack evaluator 118 begins the evaluation of an expression ed in a next child frame to be evaluated red to herein as the nt frame”). An expression is evaluated either within the stack evaluator 118 itself or needs to be processed within the application server 106 as described above in conjunction with Figure 1. 7890071__1 At step 510, the stack evaluator 118 receives a request from the inspection engine 302 to inspect the current frame. As bed above, each time a new frame is being evaluated, the tion engine analyzes a t expression that is to be evaluated within the frame to determine whether the evaluation of the expression should be executed in batch with other similar expressions. The process of inspection and batch execution is bed in detail with respect to Figures 6A and 68.
At step 512, the stack evaluator 118 determines whether the stack 202 is in a blocked state. As discussed above and described in greater detail with respect to Figures 6A and GB, for a particular stack 202, if the inspection engine 302 determines that the current expression should be evaluated in batch with other similar expressions, then the blocking engine 304 blocks the processing of the current expression and the stack 202, in general. if, at step 512, the stack evaluator 118 determines that the stack 202 is in a blocked state, then the method 500 ds to step 514, where the stack evaluator 118 waits until the stack 202 is unblocked by the unblocking engine 306. However, if, at step 512, the stack evaluator 118 determines that the stack 202 is not in a blocked state, then the method 500 proceeds to step 516, where the stack evaluator 118 tes the tion of the sion in the current frame.
At step 518, the stack evaluator 118 determines whether any child frames were generated at step 504 are still not evaluated. if so, then the method proceeds to step 508 previously described herein. if the stack evaluator 118 determines that all the child frames were generated at step 504 have been evaluated, then the method 500 proceeds to step 520. At step 520, the stack evaluator 118 determines whether the call frame that was generated at step 502 has been evaluated. if, at step 520, the stack tor 118 determines that the call frame that was generated at step 502 has not been evaluated, then the method 500 proceeds to step 522. At step 522, the stack evaluator 118 begins the evaluation of the call frame based on the expressions that were evaluated via the child frames. The method then proceeds to step 510 previously described herein. 7890071_1 if, however, at step 520, the stack evaluator 118 determines that the call frame that was generated at step 502 has y been evaluated, then the method 500 proceeds to step 524. At step 524, the stack evaluator 118 transitions the state of the the stack 202 to the completed state. The method 500 then ends.
As discussed above, the application 102 is associated with one or more m subroutines and each program tine includes multiple program instructions. Persons skilled in the art would recognize that the stack evaluator 118 executes the method steps described with respect to Figures 5A and 5B for each program instruction included in each program subroutine associated with the application 102, as discussed above.
Figures 6A and 68 set forth a flow diagram of method steps for processing related program instructions in s, according to one embodiment of the ion. Although the method steps are described in conjunction with the system for Figure 1-4, persons skilled in the art will understand that any system ured to perform the method steps, in any order, is within the scope of the invention.
The method 600 begins at step 602, where the inspection engine 302, for each stack 202, inspects an expression within the stack 202 that is to be evaluated. At step 604, the inspection engine 302, based on the inspection, identifies one or more expressions ed in the ked stacks that should be batch processed. As previously described, the inspections engine 302 identifies such expressions based on a type of the expression, the number of inputs specified in the expression, the type of operation to be performed, etc.
At step 606, the blocking engine 304 blocks the processing of the expressions identified at step 604 and the stacks 202 that e those expressions. In one embodiment, the blocking engine 304 transitions the state of each of the stacks 202 to a blocked state. At step 606, the blocking engine 304 determines whether all the stacks are in a blocked or completed state. If, at step 606, at least one stack is not in a blocked or completed state, then the 7890071_1 method 600 returns to step 602. If, however, at step 606, all the stacks are in a blocked or completed state, then the method 600 proceeds to step 610.
At step 610, the blocking engine 304 divides the expressions included in the blocked stacks into partitions, where expressions in a ular partition are each associated with at least one similar characteristic. For e, each blocked expression in a particular partition may be a database call to be executed by the application server 106. At step 612, once the blocked expressions are divided into partitions, the ng engine 304 dispatches, for each partition, a single call to the application server 106 for evaluating each of the expressions in that partition in batch. The application server 106 evaluates the expression in a manner described above in conjunction with Figure 1.
At step 614, the unblocking engine 306 receives, for each partition, the results for each expression in the partition. At step 616, for each received result, the unblocking engine 306 s the stack 202 corresponding to the expression for which the-result was generated to store the result. At step 618, the unblocking engine 306 unblocks each of the updated stacks 202, which then continue to be processed.
Advantageously, because a single batch processing request is transmitted to the application server for a group of similar expressions, the number of processing requests received by the application server is reduced.
As a result, the application server is not burdened with a large amount of requests at any given time. ore, the l processing ency of the application server is increased and the overall processing latency of the application server is reduced.
One embodiment of the invention may be implemented as a program product for use with a computer system. The program(s) of the program product define functions of the ments (including the methods described herein) and can be contained on a variety of computer-readable storage media. illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a er such as CD-ROM disks readable by a CD-ROM drive, flash memory, ROM 7890071_1 chips or any type of solid-state non—volatile semiconductor memory) on which information is permanently stored; and (ii) writable e media (e.g., floppy disks within a diskette drive or hard-disk drive or any type of solid-state random- access semiconductor memory) on which alterable information is stored.
Another embodiment of the invention may be implemented as a program product ed for use over a network. In such an embodiment, the m product may be accessed via a web browser.
The ion has been described above with reference to specific embodiments. Persons skilled in the art, however, will understand that various modifications and changes may be made thereto without ing from the broader spirit and scope of the invention as set forth in the appended claims.
The foregoing description and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 7890071_1 x

Claims (20)

We Claim:
1. A computer-implemented method to facilitate batch evaluation of a plurality of expressions, the method comprising: analyzing a first expression to be evaluated within a first call stack associated with a first instruction of a software routine, wherein the first instruction specifies the first expression; determining whether the first expression and a second expression to be evaluated within a different call stack should be batch evaluated; in response to determining that the first expression and the second expression should not be batch evaluated, evaluating the first expression and the second expression in a stack evaluator; in response to determining that the first expression and the second expression should be batch evaluated, causing the first expression and the second expression to be evaluated in an application server; receiving, from the application server, a different value for each of the first expression and the second expression that is generated when a batch processing request is processed by the application server; and populating the first call stack with the received value for the first expression.
2. The method of claim 1, wherein the different call stack is associated with a second instruction of the software routine and the second instruction specifies the second expression.
3. The method of claim 1, wherein determining that the first expression and the second expression should be batch evaluated comprises determining that the first expression is associated with a first characteristic.
4. The method of claim 3, further comprising determining that the first characteristic is included in a pre-determined list of characteristics associated with expressions that should be batch evaluated. 15 (9463428_1):GMM
5. The method of claim 4, further comprising determining that each of the first expression and the second expression is associated with the first characteristic.
6. The method of claim 3, wherein the first characteristic comprises an expression that is evaluated via a database call.
7. The method of claim 3, wherein the first characteristic comprises an expression that specifies a plurality of inputs.
8. The method of claim 1, further comprising blocking the first call stack from further processing after determining that the first expression should be batch evaluated with the second expression.
9. The method of claim 8, further comprising unblocking the first call stack after populating the first call stack with the value for the first expression.
10. A computer readable medium storing instructions that, when executed by a processor, cause the processor to facilitate batch evaluation of a plurality of expressions, by performing the steps of: analyzing a first expression to be evaluated within a first call stack associated with a first instruction of a software routine, wherein the first instruction specifies the first expression; determining whether the first expression and a second expression to be evaluated within a different call stack should be batch evaluated; in response to determining that the first expression and the second expression should not be batch evaluated, evaluating the first expression and the second expression in a stack evaluator; in response to determining that the first expression and the second expression should be batch evaluated, causing the first expression and the second expression to be evaluated in an application server; 16 (9463428_1):GMM receiving, from the application server, a different value for each of the first expression and the second expression that is generated when a batch processing request is processed by the application server; and populating the first call stack with the received value for the first expression.
11. The computer readable medium of claim 10, wherein the different call stack is associated with a second instruction of the software routine and the second instruction specifies the second expression.
12. The computer readable medium of claim 10, wherein determining that the first expression and the second expression should be batch evaluated comprises determining that the first expression is associated with a first characteristic.
13. The computer readable medium of claim 12, further comprising determining that the first characteristic is included in a pre-determined list of characteristics associated with expressions that should be batch evaluated.
14. The computer readable medium of claim 13, further comprising determining that each of the first expression and the second expression is associated with the first characteristic.
15. The computer readable medium of claim 12, wherein the first characteristic comprises an expression that is evaluated via a database call.
16. The computer readable medium of claim 12, wherein the first characteristic comprises an expression that specifies a plurality of inputs.
17. The computer readable medium of claim 10, further comprising blocking the first call stack from further processing after determining that the first expression should be batch evaluated with the second expression. 17 (9463428_1):GMM
18. The computer readable medium of claim 17, further comprising unblocking the first call stack after populating the first call stack with the value for the first expression.
19. A computer system, comprising: a memory; and a processor configured to: analyze a first expression to be evaluated within a first call stack associated with a first instruction of a software routine, wherein the first instruction specifies the first expression, determine whether the first expression and a second expression to be evaluated within a different call stack should be batch evaluated, in response to determining that the first expression and the second expression should not be batch evaluated, evaluate the first expression and the second expression in a stack evaluator, in response to determining that the first expression and the second expression should be batch evaluated, cause the first expression and the second expression to be evaluated in an application server, receive, from the application server, a different value for each of the first expression and the second expression that is generated when a batch processing request is processed by the application server, and populate the first call stack with the received value for the first expression.
20. The computer system of claim 19, wherein the different call stack is associated with a second instruction of the software routine and the second instruction specifies the second expression.
NZ616212A 2012-10-22 2013-10-02 System and method for batch evaluation programs NZ616212B (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/657635 2012-10-22
US13/657,635 US9348677B2 (en) 2012-10-22 2012-10-22 System and method for batch evaluation programs

Publications (2)

Publication Number Publication Date
NZ616212A NZ616212A (en) 2015-01-30
NZ616212B true NZ616212B (en) 2015-05-01

Family

ID=

Similar Documents

Publication Publication Date Title
US20220027195A1 (en) System and method for batch evaluation programs
US9471370B2 (en) System and method for stack-based batch evaluation of program instructions
AU2017202873B2 (en) Efficient query processing using histograms in a columnar database
US9367601B2 (en) Cost-based optimization of configuration parameters and cluster sizing for hadoop
US9477974B2 (en) Method and systems for flexible and scalable databases
US20140156683A1 (en) Integrating event processing with map-reduce
US11775520B2 (en) Updating of a denormalized database object after updating, deleting, or inserting a record in a source database object
US10191947B2 (en) Partitioning advisor for online transaction processing workloads
CN107688626A (en) Slow inquiry log processing method, device and electronic equipment
CN114443680A (en) Database management system, related apparatus, method and medium
CN107209764B (en) Rules for specifying and applying data
Almeida et al. Performance analysis and optimization techniques for oracle relational databases
US11036471B2 (en) Data grouping for efficient parallel processing
NZ616212B (en) System and method for batch evaluation programs
WO2021143199A1 (en) Method and apparatus for searching log, computer device, and storage medium
CN113377604A (en) Data processing method, device, equipment and storage medium
NZ616299B (en) System and method for batch evaluation programs
CN117193990B (en) Scheduling management method, device, equipment and storage medium of http interface
WO2024156113A1 (en) Runtime error attribution for database queries specified using a declarative database query language
US10311128B2 (en) Analytic system for fast quantile computation with improved memory consumption strategy
Hansen et al. Microsoft SQL Server 2005: Rethinking Code Placement