You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the great work! At the moment, the vHive open-source community (that is represented by 11+ universities and 4+ companies to date) is putting together a comprehensive serverless benchmark suite and we would love to see the ServerlessBench workloads (particularly, the 4 real-world apps) in vHive, as well. Once contributed, the community takes the responsibility for maintaining the suite's workloads.
Porting serverless apps to vHive is conceptually easy: one just needs to dockerize the functions/executors with an HTTP, or preferably gRPC, web server (example). It is very similar to Docker images that AWS supports today.
All non-serverless components can be deployed with stock Kubernetes manifests (e.g., here is an example with MinIO object-store deployment).
Please let me know your thoughts and let us figure out the roadmap together.
The text was updated successfully, but these errors were encountered:
Dear Maintainers,
Thank you for the great work! At the moment, the vHive open-source community (that is represented by 11+ universities and 4+ companies to date) is putting together a comprehensive serverless benchmark suite and we would love to see the ServerlessBench workloads (particularly, the 4 real-world apps) in vHive, as well. Once contributed, the community takes the responsibility for maintaining the suite's workloads.
Porting serverless apps to vHive is conceptually easy: one just needs to dockerize the functions/executors with an HTTP, or preferably gRPC, web server (example). It is very similar to Docker images that AWS supports today.
All non-serverless components can be deployed with stock Kubernetes manifests (e.g., here is an example with MinIO object-store deployment).
Please let me know your thoughts and let us figure out the roadmap together.
The text was updated successfully, but these errors were encountered: