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

vochain high level benchmark #965

Open
p4u opened this issue May 31, 2023 · 1 comment · May be fixed by #1028
Open

vochain high level benchmark #965

p4u opened this issue May 31, 2023 · 1 comment · May be fixed by #1028
Assignees

Comments

@p4u
Copy link
Member

p4u commented May 31, 2023

We need a high level benchmark for testing the vochain performance, as pointed by issue #963.

This benchmark should be as realistic as possible (without requiring a network) and execute the whole stack: app, state, indexer and api.

A good starting point is this test: https://github.com/vocdoni/vocdoni-node/blob/master/test/api_test.go#L25

We might transform this test into a benchmark where the number of votes and parallel voting routines can be specified.

The benchmark should return the tempos required for performing an election of the specified size (from the creation to the result's scrutiny).

Note that the benchmarks on benchmarks/ directory are outdated, since all of them use the old RPC interface. However they can be used as example for the new benchmark.

@altergui
Copy link
Contributor

Note that the benchmarks on benchmarks/ directory are outdated, since all of them use the old RPC interface. However they can be used as example for the new benchmark.

i did indeed notice this deprecated-but-not-reimplemented benchmarks while working on #1015.
i'll prioritise this issue next, then.

@altergui altergui linked a pull request Jul 3, 2023 that will close this issue
@altergui altergui linked a pull request Oct 17, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants