Marcin Copik

Sounds good - please ask if you find anything unclear or if the documentation is missing/incomplete.

@Rajiv2605 That looks like a bug completely unrelated to the `perf_cost` experiment - I will try to fix it tonight.

@Rajiv2605 I pushed to master a fix that should resolve the issue :) I hope that remaining issues will only be related to the `perf-cost` experiment.

@Rajiv2605 The experiment is not fully supported because certain features are not implemented in the `Local` deployment. In this example, it seems that `storage_container` is not initialized. Here, we should...

@Rajiv2605 Good progress! :-) **Issue 1** yes, likely, we do not update the cache at all. In cloud deployment, we always update the cache to store information about deployed functions,...

**Issue 3** Your approach looks correct - kill the warm containers. However, then you need to launch new containers to create deployments. The significant difference between cloud and local is...

@Rajiv2605 Thanks for the PR! I realized this issue is more complex than we initially anticipated. Nevertheless, I think you made good progress toward completion. I think the last piece...

@jchigu Local backend is primarily used for local testing and low-level measurements, e.g., with PAPI. For actual FaaS measurements, I recommend using a real FaaS platform deployed on edge, e.g.,...

@prajinkhadka Thank you for the report! We need to update the most recent Python runtimes for AWS, Azure, and GCP. I marked it as an issue for the next release...

:+1: for the problem - the interface is right now inconsistent. `as_bytes` uses `std::byte` while creating a new uuid enforce casting to `uint8_t`.