apache/openwhisk

prefetch container optimization

Open

#2,359 opened on Jun 12, 2017

View on GitHub
 (2 comments) (2 reactions) (0 assignees)Scala (6,777 stars) (1,177 forks)batch import
help wantedperformance

Description

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.

Contributor guide

Tech stack
scalakafkadocker
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
OpenWhisk architectureKafkaDockerScala
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
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.
prefetch container optimization · apache/openwhisk#2359 | Good First Issue