Skip to content

Latest commit

 

History

History
53 lines (32 loc) · 4.02 KB

File metadata and controls

53 lines (32 loc) · 4.02 KB
graph LR
    API_Controller_Orchestrator_["API Controller (Orchestrator)"]
    Worker_Information_Store["Worker Information Store"]
    Model_Serving_Workers_Inference_Worker_Nodes_["Model Serving Workers (Inference Worker Nodes)"]
    API_Controller_Orchestrator_ -- "manages" --> Worker_Information_Store
    API_Controller_Orchestrator_ -- "routes requests to" --> Model_Serving_Workers_Inference_Worker_Nodes_
    Model_Serving_Workers_Inference_Worker_Nodes_ -- "sends heartbeats to" --> API_Controller_Orchestrator_
    Model_Serving_Workers_Inference_Worker_Nodes_ -- "performs inference for" --> API_Controller_Orchestrator_
Loading

CodeBoardingDemoContact

Details

The LLaVA serving subsystem is orchestrated by the API Controller, which acts as the central hub for managing distributed model inference. It maintains a Worker Information Store to keep track of registered Model Serving Workers, enabling intelligent routing of inference requests. Model Serving Workers are responsible for executing the actual model inference and periodically sending heartbeats to the API Controller to report their status and availability. This architecture ensures efficient distribution of inference tasks and robust management of worker nodes.

API Controller (Orchestrator)

The primary component responsible for managing the registration, health, and intelligent routing of incoming inference requests to available Model Serving Workers. It acts as the central hub for distributed model inference.

Related Classes/Methods:

Worker Information Store

An internal data structure or mechanism within the API Controller that stores metadata and state for each registered worker node, including their addresses, last heartbeat times, and available models. This enables the Controller to make informed routing decisions.

Related Classes/Methods:

Model Serving Workers (Inference Worker Nodes)

Distributed computational units responsible for executing the actual model inference tasks and sending their status (heartbeats) back to the Controller.

Related Classes/Methods: