US 11,983,569 B2
Services thread scheduling based upon thread tracing
Priyanka Prakash Naik, Mumbai (IN); Kavya G, Chennai (IN); Chander Govindarajan, Chennai (IN); Sayandeep Sen, Bangalore (IN); and Palanivel Andiappan Kodeswaran, Bangalore (IN)
Assigned to International Business Machines Corporation, Armonk, NY (US)
Filed by International Business Machines Corporation, Armonk, NY (US)
Filed on Aug. 18, 2021, as Appl. No. 17/405,885.
Prior Publication US 2023/0058090 A1, Feb. 23, 2023
Int. Cl. G06F 9/50 (2006.01); G06F 9/455 (2018.01); G06F 9/48 (2006.01); G06F 11/34 (2006.01); G06N 5/01 (2023.01); G06N 5/04 (2023.01); G06N 20/00 (2019.01)
CPC G06F 9/5038 (2013.01) [G06F 9/45558 (2013.01); G06F 9/4881 (2013.01); G06F 9/5072 (2013.01); G06F 9/5077 (2013.01); G06F 11/3409 (2013.01); G06N 5/01 (2023.01); G06N 5/04 (2013.01); G06N 20/00 (2019.01); G06F 2009/4557 (2013.01); G06F 2009/45591 (2013.01); G06F 2209/505 (2013.01); G06F 2209/508 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method, comprising:
producing, for each of a plurality of containers, a resource profile for each thread in each of the plurality of containers, the resource profile including at least one resource indicator to indicate that a thread utilizes a resource represented by the resource indicator above a threshold for determining a container dependency between the thread and other threads within a single container,
wherein each thread is associated with an application hosted on a virtual environment, wherein subsets of the plurality of containers are associated with cores comprising resources for use by containers, wherein sets of containers are assigned to a node within a node cluster;
identifying, for each of the plurality of containers and from, at least in part, resource indicators in the resource profiles, container dependencies between threads on a single of the plurality of containers;
determining service dependencies between threads across different of the plurality of containers;
scheduling, based upon the container dependencies and the service dependencies, threads to the cores, wherein the scheduling is based upon minimizing thread processing times; and
publishing the container dependencies and the service dependencies on a registry of the node clusters.