Help needed to understand the execution time of a simple python function
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
Hello,
## Environment details:
* local deployment of the latest Openwhisk
## Steps to reproduce the issue:
I have a simple python function and would like to measure the cold-start latency and execution time for warm, pre-warm, and cold start conditions.
1. For measuring the cold-start latency, I have used the init time reported in the wsk activation get command.
2. For measuring the actual function execution, I have used $duration-init$.
I found the actual function execution is higher in the case of cold and pre-warm conditions compared to warm. While the initialization time follows the order cold>pre-warm.
I do not understand why the actual function execution time differs between all three conditions. Isn't it should be the same across all the conditions.
Could someone please explain why it is different across the various container states?
Any help is appreciated. Thank you in advance.
Contributor guide
Research direction
Start with the local OpenWhisk deployment and the `wsk activation get ` output, focusing on `init` and `$duration-init$` for warm, pre-warm, and cold conditions. The issue names no source files or tests; it would need a clear explanation of the timing differences before any documentation change could be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100