Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out how to copy data from coordinator to seeders #1068

Closed
gmega opened this issue Jan 15, 2025 · 1 comment
Closed

Figure out how to copy data from coordinator to seeders #1068

gmega opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
Client See https://miro.com/app/board/uXjVNZ03E-c=/ for details

Comments

@gmega
Copy link
Member

gmega commented Jan 15, 2025

I started under the assumption that the test runner and the Deluge nodes would be able to share a filesystem (that was the initial plan with Wings), but:

  1. this creates performance artifacts, particularly if we're mounting the same persistent for everyone;
  2. Hetzner doesn't support ReadWriteMany.

We therefore need to change approach. While I could generate data locally at the clients, this would mean modifying the client images for an experiment, which I don't want to do. I'm therefore going to try to use the Kubernetes Python client and implement a different uploader.

I'll also adjust the PVCs so they use local storage. This should eliminate performance artifacts.

@gmega gmega self-assigned this Jan 15, 2025
@gmega gmega added the Client See https://miro.com/app/board/uXjVNZ03E-c=/ for details label Jan 15, 2025
@gmega
Copy link
Member Author

gmega commented Jan 23, 2025

This was fixed by codex-storage/bittorrent-benchmarks#2

@gmega gmega closed this as completed Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client See https://miro.com/app/board/uXjVNZ03E-c=/ for details
Projects
None yet
Development

No branches or pull requests

1 participant