US2018027060A1PendingUtilityA1

Technologies for determining and storing workload characteristics

Assignee: METSCH THIJSPriority: Jul 22, 2016Filed: Jan 17, 2017Published: Jan 25, 2018
Est. expiryJul 22, 2036(~10 yrs left)· nominal 20-yr term from priority
G06F 15/161G06F 2212/1024H04Q 2011/0079H05K 2201/10121G06F 2212/1041Y10S901/01H05K 2201/066G06F 2209/5019H04Q 2011/0052H04Q 2011/0086H04L 41/5019H04Q 2011/0073H04Q 2213/13523H04Q 2213/13527G06F 2209/5022H05K 2201/10159H04Q 2011/0041H05K 7/1485G06F 3/067G06F 3/0619G06F 3/065G06F 3/0659H04Q 1/09H04L 49/35G06F 2209/483G06F 9/5027G06F 9/4881G06F 13/385H03M 7/6023H04Q 11/00G08C 2200/00G08C 17/02H04L 47/782H03M 7/40Y02P90/30G06Q 10/06H04L 45/52H03M 7/6005H03M 7/4031H03M 7/4081G06Q 10/06314H04L 49/15H04L 49/357G06Q 10/20H04L 47/38G06Q 50/04G06Q 10/087H04L 45/02H04L 41/12H04L 47/805H04L 67/1008H04L 67/12H04L 41/145G02B 6/3897G06F 13/4022H04L 41/149H04L 41/40H04L 47/83G06F 3/061H04J 14/00H03M 7/3084G06F 9/3887G06F 9/30036G06F 16/1748H04L 67/51H04L 61/00H04L 69/18G06F 13/42G06F 13/409G06F 13/4068Y10S901/30Y04S10/52H04L 43/065G06F 2212/202G06F 3/0625G06F 1/20H04Q 2011/0037G06F 8/65H04Q 11/0003H04L 49/45G06F 3/0688H04L 43/0876G06F 9/4401Y04S10/50G06F 2212/152G06F 3/0679G06F 3/0683G06F 16/9014G06F 13/1668H04L 43/0817H04L 69/329G11C 7/1072G06F 2212/402H04W 4/80G06F 3/0655G06F 1/183G02B 6/3893H04L 43/0894H04B 10/25891G06F 3/0653G06F 12/109G11C 11/56H04L 67/02G06F 3/064H04L 67/306G06F 2212/7207G02B 6/4292H04L 49/00G06F 3/0664H05K 7/1442H03M 7/4056G06F 9/544H04L 49/25G06F 3/0689G02B 6/3882G06F 3/0673G06F 3/0665H03M 7/3086G06F 12/1408H04B 10/25G06F 2212/1044H04L 69/04G06F 2212/1008G11C 5/02G06F 3/0613G11C 14/0009H05K 2201/10189G06F 2212/401Y02D10/00G06F 3/0616G06F 3/0631G06F 3/0638G06F 3/0647G06F 9/5016G06F 9/5072H04L 43/16H04L 47/24H04L 67/1004H04L 67/1034H04L 67/1097H04Q 11/0071H05K 5/0204H05K 7/1489H05K 7/1491G06F 3/0658H05K 7/1498H04L 41/0813H04L 67/1029H04Q 11/0005G06F 9/505G06F 3/0611H04L 41/082H04L 67/34H04L 67/1012B25J 15/0014B65G 1/0492H05K 7/1492H05K 7/20736H04L 49/555H04L 67/10H04Q 11/0062H04W 4/023G06F 13/4282H05K 1/181H05K 7/2039H05K 7/20709H05K 7/1418H05K 7/1461G05D 23/1921G05D 23/2039H05K 7/20727H05K 7/20745H05K 7/20836G06F 9/5044H05K 1/0203H05K 7/1487H04Q 1/04G06F 12/0893H05K 13/0486G06F 13/1694G11C 5/06H03M 7/30H05K 7/1421H05K 7/1422H05K 7/1447G06F 11/141G06F 11/3414G06F 12/0862G06F 15/8061H04L 47/765H04L 67/1014G06F 9/5077G06F 12/10G06F 13/161G07C 5/008H04L 12/2809H04L 41/024H04L 9/0643H04L 9/14H04L 9/3247H04L 9/3263H04L 47/82H04L 41/046
71
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Technologies for determining and storing workload characteristics include an orchestrator server to identify a workload to be executed by a managed node, obtain a profile associated with the workload, wherein the profile includes a model that relates an input parameter set indicative of one of more characteristics of the workload with an output parameter set indicative of one or more aspects of resources to be allocated for execution of the workload, determine, as a function of the input parameter set and the model, resources to allocate to the managed node to execute the workload, and allocate the determined resources to the managed node to execute the workload. Other embodiments are also described and claimed.

Claims

exact text as granted — not AI-modified
1 . An orchestrator server to manage workload profiles, the orchestrator server comprising:
 one or more processors;   one or more memory devices having stored therein a plurality of instructions that, when executed by the one or more processors, cause the orchestrator server to:
 identify a workload to be executed by a managed node; 
 obtain a profile associated with the workload, wherein the profile includes a model that relates an input parameter set indicative of one or more characteristics of the workload with an output parameter set indicative of one or more aspects of resources to be allocated for execution of the workload; 
 determine, as a function of the input parameter set and the model, resources to allocate to the managed node to execute the workload; and 
 allocate the determined resources to the managed node to execute the workload. 
   
     
     
         2 . The orchestrator server of  claim 1 , wherein the plurality of instructions, when executed, further cause the orchestrator server to:
 receive telemetry data indicative of resource utilization and workload performance as the workload is executed;   determine, as a function of the telemetry data, whether one or more threshold objectives are satisfied by the execution of the workload with the allocation of resources;   adjust, in response to a determination that the one or more threshold objectives are not satisfied, the allocation of resources to the managed node to satisfy the one or more threshold objectives; and   adjust the model to include the adjustment to the allocation of resources.   
     
     
         3 . The orchestrator server of  claim 2 , wherein to adjust the model comprises to adjust the model to produce an output parameter set of resources that represents the adjusted allocation of resources, in response to the input parameter set. 
     
     
         4 . The orchestrator server of  claim 2 , wherein to adjust the model comprises to adjust the output parameter set to change one or more architecture features of the resources to be allocated, wherein the architecture features include one or more of support for an extended instruction set, support for preloading of processor cache with one or more predefined values, support for accelerated cryptographic operations, and support for accelerated data compression operations. 
     
     
         5 . The orchestrator server of  claim 2 , wherein the plurality of instructions, when executed, further cause the orchestrator server to:
 generate, as a function of the telemetry data, landscape data indicative of conditions across the set of managed nodes in a data center; and   wherein to determine whether the threshold objectives are satisfied comprises to determine whether the threshold objectives are satisfied based additionally on the landscape data.   
     
     
         6 . The orchestrator server of  claim 2 , wherein the plurality of instructions, when executed, further cause the orchestrator server to:
 obtain resource allocation objective data indicative of one or more thresholds to be satisfied during the execution of the workload; and   wherein to determine whether the execution of the workload satisfies one or more threshold objectives comprises to determine whether the execution of the workload satisfies the resource allocation objective data.   
     
     
         7 . The orchestrator server of  claim 6 , wherein to obtain the resource allocation objective data comprises to obtain one or more thresholds indicative of a target power consumption, a target life expectancy, a target heat production, and a target performance of one or more resources allocated to the managed node. 
     
     
         8 . The orchestrator server of  claim 2 , wherein to adjust the resource allocation to satisfy the one or more threshold objectives comprises to adjust one or more settings of one or more architecture features of the allocated resources. 
     
     
         9 . The orchestrator server of  claim 2 , wherein to obtain a profile comprises to obtain a profile that includes a model that relates an input parameter set that is further indicative of a type of the workload, a category of the workload, resource utilization behavior, or one or more of the threshold objectives to be satisfied during the execution of the workload to the output parameter set. 
     
     
         10 . The orchestrator server of  claim 1 , wherein to obtain a profile associated with the workload comprises to obtain a profile that includes a model that relates the input parameter set with an output parameter set that is further indicative of a target location of the resources. 
     
     
         11 . The orchestrator server of  claim 1 , wherein to determine the resources to allocate comprises to select, from the profile, a pre-stored output parameter set mapped to the input parameter set. 
     
     
         12 . The orchestrator server of  claim 1 , wherein to obtain the profile comprises to:
 determine whether a pre-stored profile is associated with the workload; and   generate, in response to a determination that a pre-stored profile is not associated with the workload, the profile from a reference profile.   
     
     
         13 . The orchestrator server of  claim 1 , wherein to identify the workload to be executed by the managed node comprises to receive a request from a client device to execute the workload. 
     
     
         14 . The orchestrator server of  claim 13 , wherein to obtain the profile comprises to receive the profile with the request from the client device. 
     
     
         15 . One or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause an orchestrator server to:
 identify a workload to be executed by a managed node;   obtain a profile associated with the workload, wherein the profile includes a model that relates an input parameter set indicative of one or more characteristics of the workload with an output parameter set indicative of one or more aspects of resources to be allocated for execution of the workload;   determine, as a function of the input parameter set and the model, resources to allocate to the managed node to execute the workload; and   allocate the determined resources to the managed node to execute the workload.   
     
     
         16 . The one or more machine-readable storage media of  claim 15 , wherein the plurality of instructions, when executed, further cause the orchestrator server to:
 receive telemetry data indicative of resource utilization and workload performance as the workload is executed;   determine, as a function of the telemetry data, whether one or more threshold objectives are satisfied by the execution of the workload with the allocation of resources;   adjust, in response to a determination that the one or more threshold objectives are not satisfied, the allocation of resources to the managed node to satisfy the one or more threshold objectives; and   adjust the model to include the adjustment to the allocation of resources.   
     
     
         17 . The one or more machine-readable storage media of  claim 16 , wherein to adjust the model comprises to adjust the model to produce an output parameter set of resources that represents the adjusted allocation of resources, in response to the input parameter set. 
     
     
         18 . The one or more machine-readable storage media of  claim 16 , wherein to adjust the model comprises to adjust the output parameter set to change one or more architecture features of the resources to be allocated, wherein the architecture features include one or more of support for an extended instruction set, support for preloading of processor cache with one or more predefined values, support for accelerated cryptographic operations, and support for accelerated data compression operations. 
     
     
         19 . The one or more machine-readable storage media of  claim 16 , wherein the plurality of instructions, when executed, further cause the orchestrator server to:
 generate, as a function of the telemetry data, landscape data indicative of conditions across the set of managed nodes in a data center; and   wherein to determine whether the threshold objectives are satisfied comprises to determine whether the threshold objectives are satisfied based additionally on the landscape data.   
     
     
         20 . The one or more machine-readable storage media of  claim 16 , wherein the plurality of instructions, when executed, further cause the orchestrator server to:
 obtain resource allocation objective data indicative of one or more thresholds to be satisfied during the execution of the workload; and   wherein to determine whether the execution of the workload satisfies one or more threshold objectives comprises to determine whether the execution of the workload satisfies the resource allocation objective data.   
     
     
         21 . The one or more machine-readable storage media of  claim 20 , wherein to obtain the resource allocation objective data comprises to obtain one or more thresholds indicative of a target power consumption, a target life expectancy, a target heat production, and a target performance of one or more resources allocated to the managed node. 
     
     
         22 . The one or more machine-readable storage media of  claim 16 , wherein to adjust the resource allocation to satisfy the one or more threshold objectives comprises to adjust one or more settings of one or more architecture features of the allocated resources. 
     
     
         23 . The one or more machine-readable storage media of  claim 16 , wherein to obtain a profile comprises to obtain a profile that includes a model that relates an input parameter set that is further indicative of a type of the workload, a category of the workload, resource utilization behavior, or one or more of the threshold objectives to be satisfied during the execution of the workload to the output parameter set. 
     
     
         24 . The one or more machine-readable storage media of  claim 15 , wherein to obtain a profile associated with the workload comprises to obtain a profile that includes a model that relates the input parameter set with an output parameter set that is further indicative of a target location of the resources. 
     
     
         25 . A orchestrator server to manage workload profiles, the orchestrator server comprising:
 means for identifying a workload to be executed by a managed node;   means for obtaining a profile associated with the workload, wherein the profile includes a model that relates an input parameter set indicative of one or more characteristics of the workload with an output parameter set indicative of one or more aspects of resources to be allocated for execution of the workload;   means for determining, as a function of the input parameter set and the model, resources to allocate to the managed node to execute the workload; and   circuitry for allocating the determined resources to the managed node to execute the workload.   
     
     
         26 . A method for managing workload profiles, the method comprising:
 identifying, by an orchestrator server, a workload to be executed by a managed node;   obtaining, by the orchestrator server, a profile associated with the workload, wherein the profile includes a model that relates an input parameter set indicative of one or more characteristics of the workload with an output parameter set indicative of one or more aspects of resources to be allocated for execution of the workload;   determining, by the orchestrator server and as a function of the input parameter set and the model, resources to allocate to the managed node to execute the workload; and   allocating, by the orchestrator server, the determined resources to the managed node to execute the workload.   
     
     
         27 . The method of  claim 26 , further comprising:
 receiving, by the orchestrator server, telemetry data indicative of resource utilization and workload performance as the workload is executed;   determining, by the orchestrator server and as a function of the telemetry data, whether one or more threshold objectives are satisfied by the execution of the workload with the allocation of resources;   adjusting, by the orchestrator server and in response to a determination that the one or more threshold objectives are not satisfied, the allocation of resources to the managed node to satisfy the one or more threshold objectives; and   adjusting, by the orchestrator server, the model to include the adjustment to the allocation of resources.   
     
     
         28 . The method of  claim 27 , wherein adjusting the model comprises adjusting the model to produce an output parameter set of resources that represents the adjusted allocation of resources, in response to the input parameter set.

Join the waitlist — get patent alerts

Track US2018027060A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.