Skip to content
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.

Baseline benchmark of upload and download success rate #1033

Closed
adamschmideg opened this issue Nov 29, 2018 · 3 comments
Closed

Baseline benchmark of upload and download success rate #1033

adamschmideg opened this issue Nov 29, 2018 · 3 comments
Assignees
Labels

Comments

@adamschmideg
Copy link

adamschmideg commented Nov 29, 2018

The idea here is to run continuously the swarm-smoke tests towards a given environment (https://swarm-gateways.net/ or a given deployment on Kubernetes), and also pushing the success or failure measurements to InfluxDB/Grafana.

So we need:

  1. Cronjobs to run as part of a deployment of Swarm (https://github.com/ethereum/swarm-cluster/pull/90), for example:
  • 100kb content (every 10min)?
  • 1000kb content (every 1 hour)?
  • 10000kb content (every 2-3 hours)?
  1. Modify swarm-smoke to push success/failure measurements to InfluxDB, as well as times that it took to upload and time that it took for the test to finish. cmd/swarm: add flag for application name (swarm or swarm-private) ethereum/go-ethereum#18189

  2. We should probably modify swarm-smoke to not always download concurrently from all nodes a given content upload, but to randomly pick a node and download only from it. Otherwise we are going to have a lot of the content cached on individual nodes, which might hide issues with retrieve requests.

@nonsense
Copy link
Contributor

nonsense commented Dec 3, 2018

  1. Cronjob is ready. swarm-private: add smoke test cron job helm-charts#13

  2. We are in the process of adding configurations and flags to the smoke tests. cmd/swarm/swarm-smoke: timeout flag #1041

@nonsense
Copy link
Contributor

What's left to do for this ticket is https://github.com/ethereum/swarm-cluster/issues/103 and then we can close it.

@adamschmideg
Copy link
Author

Done

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants