Method and apparatus to use DRAM as a cache for slow byte-addressible memory for efficient cloud applications
US-12174739-B2 · Dec 24, 2024 · US
US2016098293A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016098293-A1 |
| Application number | US-201514967739-A |
| Country | US |
| Kind code | A1 |
| Filing date | Dec 14, 2015 |
| Priority date | May 5, 2009 |
| Publication date | Apr 7, 2016 |
| Grant date | — |
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.
This disclosure provides various embodiments of software, systems, and techniques for controlled interruption of batch job processing. In one instance, a tangible computer readable medium stores instructions for managing batch jobs, where the instructions are operable when executed by a processor to identify an interruption event associated with a batch job queue. The instructions trigger an interruption of an executing batch job within the job queue such that the executed portion of the job is marked by a restart point embedded within the executable code. The instructions then restart the interrupted batch job at the restart point.
Opening claim text (preview).
1 - 20 . (canceled) 21 . A non-transitory computer readable medium storing instructions for managing batch jobs, the instructions operable when executed by a processor to: execute a first batch job within a job queue, the first batch job including one or more tasks; identify a restart point placed at a predetermined location included by the first batch job prior to execution of the first batch job; identify a second batch job to be executed while the first batch job is executing; trigger an interruption event of the first batch job within the job queue; in response to the interruption event, continue a complete execution of a currently executing task for the first batch job without interruption until the restart point is reached and terminates when the restart point is reached; execute the second batch job when the first batch job has terminated; and restart the first batch job at the restart point when the second batch job has executed. 22 . The computer readable medium of claim 21 , the instructions further operable to: receive resuming data associated with the first batch job when the first batch job is interrupted; and provide the resuming data to the first batch job when the first batch job is restarted. 23 . The computer readable medium of claim 22 , the resuming data comprising a batch job identifier and a restart point identifier. 24 . The computer readable medium of claim 22 , the instructions further operable to store the resuming data in a database. 25 . The computer readable medium of claim 21 , the instructions further operable to identify the second batch job from among a plurality of batch jobs according to a job priority. 26 . The computer readable medium of claim 25 , wherein the job priority is at least one of a job execution priority or an interruption priority. 27 . The computer readable medium of claim 21 , wherein the second batch job is a higher priority batch job than the first batch job, and wherein the interruption event comprises an execution request of the higher priority batch job. 28 . The computer readable medium of claim 21 , wherein the first batch job has a larger load level than the second batch job. 29 . The computer readable medium of claim 21 , wherein the second batch job includes a second restart point, and wherein the instructions further operable to: identify a third batch job to be executed while the second batch job is executing; trigger a second interruption event of the second batch job within the job queue such that the second batch job executes until the second restart point is reached and terminates when the second restart point is reached; execute the third batch job when the second batch job has terminated; and restart the second batch job at the second restart point when the third batch job has terminated. 30 . The computer readable medium of claim 21 , wherein the second batch job includes a second restart point, and wherein the instructions further operable to: receive a request to restart the first batch job; trigger a second interruption event of the second batch job within the job queue such that the second batch job executes until the second restart point is reached and terminates when the second restart point is reached; and restart the first batch job at the first restart point. 31 . The computer readable medium of claim 21 , the first batch job comprising a business application injected with an interrupt framework. 32 . The computer readable medium of claim 31 , the instructions further operable to register the business application via the interrupt framework. 33 . The computer readable medium of claim 32 , the registration comprising an optional flag that is set at execution time via the interrupt framework. 34 . The computer readable medium of claim 21 , the instructions comprising a portion of a batch job scheduler managing a plurality of job queues. 35 . A computer implemented method for managing batch jobs, the method comprising: determining that a first batch job within a job queue is executing, wherein the first batch job includes one or more tasks; identify a restart point placed at a predetermined location included by the first batch job prior to the first batch job executing; identifying a second batch job to be executed while the first batch job is executing; triggering an interruption event of the first batch job within the job queue; in response to the interruption event, continue a complete execution of a currently executing task for the first batch job without interruption until the restart point is reached and terminates when the restart point is reached; determining that the second batch job is executing when the first batch job has terminated; and restarting the first batch job at the restart point when the second batch job has executed. 36 . The computer implemented method of claim 15 , further comprising: receiving resuming data associated with the first batch job when the first batch job is interrupted, the resuming data comprising a batch job identifier and a restart point identifier; persisting the resuming data; and providing the resuming data from persistence to the first batch job when the first batch job is restarted. 37 . The computer implemented method of claim 35 , further comprising identifying the second batch job from among a plurality of batch jobs according to a job priority, the job priority selected from a job execution priority or an interrupt priority or both. 38 . The computer implemented method of claim 35 , wherein the second batch job is a higher priority batch job than the first batch job, and wherein the interruption event comprises an execution request of the higher priority batch job. 39 . The computer implemented method of claim 35 , wherein the second batch job includes a second restart point, and wherein the method further comprises: identifying a third batch job to be executed while the second batch job is executing; triggering a second interruption event of the second batch job within the job queue such that the second batch job executes until the second restart point is reached and terminates when the second restart point is reached; executing the third batch job when the second batch job has terminated; and restarting the second batch job at the second restart point when the third batch job has terminated. 40 . The computer implemented method of claim 35 , the first batch job comprising a business application injected with an interrupt framework and the method further comprising registering the business application via the interrupt framework, the registration comprising an optional flag that is set at execution time via the framework.
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
Priority circuits therefor · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.