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

[feature]: Add synctest to our loadtest suite #1313

Open
GeorgeTsagk opened this issue Jan 22, 2025 · 0 comments · May be fixed by #1352
Open

[feature]: Add synctest to our loadtest suite #1313

GeorgeTsagk opened this issue Jan 22, 2025 · 0 comments · May be fixed by #1352
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@GeorgeTsagk
Copy link
Member

Description

We currently have loadtests for minting and sending assets. One other aspect of tapd we want to loadtest is the universe. The purpose of a synctest is to fetch data from a universe server based on certain configurations.

To keep the topology simple, we won't have on-demand tapd nodes performing the client requests to the universe, instead we'll use lite golang client code that performs the RPC requests directly. We don't really care about handling the responses, we just want to make sure we perform them. The purpose is to emulate a full-sync by multiple clients.

The configuration could include things like whether we're doing a full sync or not, number of clients, or number of syncs per client.

@GeorgeTsagk GeorgeTsagk added the enhancement New feature or request label Jan 22, 2025
@GeorgeTsagk GeorgeTsagk added this to the v0.7 milestone Jan 22, 2025
@GeorgeTsagk GeorgeTsagk self-assigned this Jan 22, 2025
@levmi levmi moved this from 🆕 New to 🏗 In progress in Taproot-Assets Project Board Feb 3, 2025
@GeorgeTsagk GeorgeTsagk linked a pull request Feb 4, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

1 participant