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

Run performance tests with dedicated network services #52

Open
ThetaSinner opened this issue Jun 17, 2024 · 1 comment
Open

Run performance tests with dedicated network services #52

ThetaSinner opened this issue Jun 17, 2024 · 1 comment
Assignees

Comments

@ThetaSinner
Copy link
Member

We should not use production network services (signal + TURN) for performance testing because

  1. It will affect production users to put heavy load on them.
  2. Sharing these services will affect results. It wouldn't invalidate them exactly, but it would make the results harder to interpret and make them more variable.

We need to decide what to run and where, then switch over the conductor-config.yaml that gets used by trycp scenarios to configure network services for trycp-spawned conductors.

@ThetaSinner
Copy link
Member Author

Low priority for now because we think the production services will scale

  • keep an eye on cloudflare billing for sbd
  • keep using runid for network seeds to keep test runs separate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
Development

No branches or pull requests

2 participants