Speedup engine and pilorama tests #651
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#651
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Our tests take >4m to execute on CI
It seems the longest ones are for engine and pilorama.
Lets try, to make them faster.
Let's leave this task to link with and close it after we have at least <2m test execution time or no longer have any ideas.
Refs #615
Analysis of the execution time showed that:
Local launch
make test
on SSD was sped up by 20% #827Long test runs on CI are related to disk operation speed. Using
WithNoSync
in tests didn't yield significant results. The execution time on an unoccupied runner formake test
is 35s. Two parallelmake test
runs take 1m15s, suggesting a bottleneck in the runner. As a temporary solution, we can consider reducing the number of tasks that run at the same time from 64 to 5-10