apache/openwhisk

prefetch container optimization

Open

#2,359 建立於 2017年6月12日

在 GitHub 查看
 (2 留言) (2 反應) (0 負責人)Scala (6,777 star) (1,177 fork)batch import
help wantedperformance

描述

To reduce cold start overhead -- if we have a good reason to believe that an action will be invoked soon -- then send a message to /init a container. I think this could be done by adding "init" messages to the kafka protocol. When receiving an "init" message, the invoker would /init a container if none is present already.

The obvious use case is sequences -- when a sequence is run, "init" all the actions in the sequence immediately.

貢獻者指南

技術棧
scalakafkadocker
領域
backendperformance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
OpenWhisk architectureKafkaDockerScala
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate the existing Kafka protocol in the invoker (likely in the invoker component) to understand current message types and handling. Examine how /init is called for containers. Design an 'init' message type and its processing logic, focusing on the sequence use case where all action containers are pre initialized. Consider performance implications and potential race conditions.