Application-Centric Benchmarking of Distributed FaaS Platforms using BeFaaS

TL;DR

This paper presents an enhanced, application-centric benchmarking framework called BeFaaS for evaluating distributed FaaS platforms, providing detailed insights into performance factors like latency and cold start times across cloud and edge environments.

Contribution

The paper extends BeFaaS with features for distributed setups, designs new realistic benchmarks, and conducts comprehensive experiments on major cloud and edge FaaS platforms.

Findings

Network transmission significantly impacts response latency.

Hybrid edge-cloud deployments exacerbate latency issues.

Azure Functions exhibits the best cold start performance.

Abstract

Due to the popularity of the FaaS programming model, there is now a wide variety of commercial and open-source FaaS systems. Hence, for comparison of different FaaS systems and their configuration options, FaaS application developers rely on FaaS benchmarking frameworks. Existing frameworks, however, tend to evaluate only single isolated aspects, a more holistic application-centric benchmarking framework is still missing. In previous work, we proposed BeFaaS, an extensible application-centric benchmarking framework for FaaS environments that focuses on the evaluation of FaaS platforms through realistic and typical examples of FaaS applications. In this extended paper, we (i) enhance our benchmarking framework with additional features for distributed FaaS setups, (ii) design application benchmarks reflecting typical FaaS use cases, and (iii) use them to run extensive experiments with commercial cloud FaaS platforms (AWS Lambda, Azure Functions, Google Cloud Functions) and the tinyFaaS edge serverless platform. BeFaaS now includes four FaaS application-centric benchmarks, is extensible for additional workload profiles and platforms, and supports federated benchmark runs in which the benchmark application is distributed over multiple FaaS systems while collecting fine-grained measurement results for drill-down analysis. Our experiment results show that (i) network transmission is a major contributor to response latency for function chains, (ii) this effect is exacerbated in hybrid edge-cloud deployments, (iii) the trigger delay between a published event and the start of the triggered function ranges from about 100ms for AWS Lambda to 800ms for Google Cloud Functions, and (iv) Azure Functions shows the best cold start behavior for our workloads.