Scale computing in deterministic cloud environments
US-2024370302-A1 · Nov 7, 2024 · US
US11394802B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11394802-B2 |
| Application number | US-202016911126-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 24, 2020 |
| Priority date | Jun 24, 2020 |
| Publication date | Jul 19, 2022 |
| Grant date | Jul 19, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method and system of providing estimates or recommendations for software lifecycle management tasks by obtaining and storing local timing and result data for a current run of an application task on a local client, and gathering global timing and result data in a server computer for a plurality of clients including the local client. The local client combines its local timing and result data with the global timing and result data to generate an estimated time completion and success probability for a next run of the application task. The local client uses a rule definition file to substitute function variables for text strings and recommendation text with the appropriate values from the combined timing and result data and outputs the final time estimate UI string and recommendation through a user interface for display to a user.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method of providing estimated completion time and success probability of applications on a client computer, comprising: providing an operations server in a data backup system processing large numbers of data assets, and that maintains a database storing aggregate and global timing and result data for the backup system; embedding an operation component in an instance of an application in the client computer, and communicably coupled to the operations server; obtaining, by the operation component, local timing and result data for a current run of the application on the client computer, the local timing data comprising elapsed time durations between machine-generated start and end timestamps for the current run; storing the local timing and result data in a first table of a client database; associating, with the local timing and result data, a context comprising operational or configuration properties that have at least some effect the elapsed time durations; sending the local timing and result data to the operations server computer for aggregation with other local client timing and result data to form global timing and result data; receiving, by the client computer, the global timing and result data from the server computer; and combining the local timing and result data with the aggregated timing and result data to generate an estimated time completion and success probability for a next run of the application task. 2. The method of claim 1 further comprising displaying the estimated time completion and success probability for display to a user through a user interface of the client computer, and wherein the estimated time completion is calculated from timing data comprising an average duration, minimum duration, maximum duration, and standard deviation of duration for the task. 3. The method of claim 2 further comprising making one or more recommendations to improve the timing and result data based on certain aggregated data. 4. The method of claim 1 further comprising determining if there is a conflict between the local timing and result data and the other local client and result data and, if so, using the local timing and result data to form the global timing and result data. 5. The method of claim 1 wherein the context is defined by a plurality of data element fields including: application version number, system configuration, data size, and storage size. 6. The method of claim 1 further comprising: grouping application tasks for the client computer and other client computers into grouped tasks based on a respective context of each application task. 7. The method of claim 1 wherein the local timing data includes the elapsed time duration and an average time calculated from the elapsed time. 8. The method of claim 1 wherein a quantum is named using a text string having a format: (Workflow Name).(Operation Name).(Quantum Name), and wherein a subset of the text string specifies the aggregate data for all entries at respective level of workflow, operation, and quantum. 9. The method of claim 1 wherein the application task is part of a lifecycle management process for a software product, and comprises a program having a finite completion time and an uncertain chance of success, and that can block full use of the client computer by a user during its execution. 10. A method of providing estimated time duration and success probability for future application program runs on a client computer, comprising: providing an operations server computer in a data backup system processing large numbers of data assets, and that maintains a database storing aggregate and global timing and result data for the backup system; embedding an operation component in an instance of an application in the client computer, and communicably coupled to the operations server; obtaining and storing, by the operation component, local timing and result data for a current run of an application task on a local client, the local timing data comprising elapsed time durations between machine-generated start and end timestamps for the current run; gathering global timing and result data in the operations server computer for a plurality of clients including the local client; combining, in the local client, the local timing and result data with the global timing and result data from the operations server computer to calculate an estimated time completion and success probability for a next run of the application task; associating, with the local timing and result data, a context comprising operational or configuration properties that have at least some effect the elapsed time durations; and generating a text message for display through a user interface displaying the result data for estimated time completion and success probability. 11. The method of claim 10 further comprising displaying usage recommendations for the next run through an additional text message displayed through the user interface. 12. The method of claim 11 further comprising using, in the client computer, a rule definition file to substitute function variables for text strings with the appropriate values from the combined timing and result data to output a final time estimate text string, a final success probability value, and recommendation text string through the user interface for display to a user. 13. The method of claim 10 wherein the application program is part of a lifecycle management process for a software product, and comprises a program having a finite completion time and an uncertain chance of success, and that can block full use of the client computer by a user during its execution, and wherein the task is smallest granularity element of a program hierarchy comprising a plurality of tasks within an operation and a plurality of operations within a workflow. 14. The method of claim 13 further comprising creating a quantum from the task by associating timing duration data associated with completion of the task and a success or failure result of the task. 15. The method of claim 14 further comprising associating the context with the quantum. 16. A system providing estimated completion time and success probability of applications, comprising: an operations server in a data backup system processing large numbers of data assets and maintaining a database storying aggregate and global timing and result data for the backup system; a client computer obtaining local timing and result data for a current run of an application task executed on the client computer, the local timing data comprising elapsed time durations between machine-generated start and end timestamps for the current run; an operation component embedded in an instance of an application in the client computer, and communicably coupled to the operations server; a client database storing the local timing and result data in a first table, and further associating, with the local timing and result data, a context comprising operational or configuration properties that have at least some effect the elapsed time durations; an interface sending the local timing and result data to the operations server computer for aggregation with other local client timing and result data to form global timing and result data, the interface receiving back the global timing and result data from the server computer; a processing component of the client computer combining the local timing and result data with the aggregated timing and result data to generate an estimated time completion and success probability for a next run of the application task; and a user int
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Establishing a time schedule for servicing the requests · CPC title
Performance evaluation by statistical analysis · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.