Page MenuHomePhabricator

[services] Tests - Backup - Initialize performance tests
ClosedPublic

Authored by karol on Jul 26 2022, 2:33 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 16, 7:19 AM
Unknown Object (File)
Mon, Dec 16, 7:19 AM
Unknown Object (File)
Mon, Dec 16, 7:19 AM
Unknown Object (File)
Mon, Dec 16, 7:19 AM
Unknown Object (File)
Mon, Dec 16, 7:19 AM
Unknown Object (File)
Sun, Dec 15, 4:54 PM
Unknown Object (File)
Sun, Dec 15, 4:54 PM
Unknown Object (File)
Sun, Dec 15, 4:54 PM

Details

Summary

Depends on D4585

Initializing performance tests for the backup service. This just generates the data to be sent and sets up a basic structure of the code

Test Plan
cd services
yarn run-performance-tests backup 1

This should compile but it will not do anything really.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

karol edited the test plan for this revision. (Show Details)
karol added reviewers: tomek, varun.
karol added inline comments.
services/commtest/tests/backup_performance_test.rs
62–99 ↗(On Diff #14923)

This should go in a separate diff

karol added inline comments.
services/commtest/tests/backup_performance_test.rs
24–29 ↗(On Diff #14923)

Should be changed like in D4581

karol edited the summary of this revision. (Show Details)

change number of threads

We can consider extracting some common logic from this and D4581. We can e.g. create a function that determines number of threads and use it in both places.

services/commtest/tests/backup_performance_test.rs
15–19

The variable is duplicated

This revision is now accepted and ready to land.Jul 26 2022, 4:35 AM
In D4631#133050, @tomek wrote:

We can consider extracting some common logic from this and D4581. We can e.g. create a function that determines number of threads and use it in both places.

Ok