Speedup engine and pilorama tests #651

New Issue

Closed

opened 2023-08-25 09:44:22 +00:00 by fyrchik · 2 comments

fyrchik commented

2023-08-25 09:44:22 +00:00

Owner

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.

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.

fyrchik added the

frostfs-node

triage

Infrastructure

labels 2023-08-25 09:44:22 +00:00

fyrchik commented

2023-08-25 09:44:52 +00:00

Poster

Owner

Refs #615

fyrchik added this to the v0.38.0 milestone 2023-08-25 09:50:50 +00:00

achuprov referenced this issue

2023-11-27 09:25:21 +00:00

engine: Speedup tests #827

fyrchik referenced this issue from a commit

2023-11-30 13:19:46 +00:00

[#651] shard/test: Refactor Shard_Delete

fyrchik referenced this issue from a commit

2023-11-30 13:19:46 +00:00

[#651] shard/test: Speedup Shard_Delete

fyrchik referenced this issue from a commit

2023-11-30 13:19:46 +00:00

[#651] engine/test: Speedup StorageEngine_Inhume

achuprov commented

2023-12-08 08:56:55 +00:00

Collaborator

Analysis of the execution time showed that:

Local launch make test on SSD was sped up by 20% #827
Long 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 for make test is 35s. Two parallel make 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

Analysis of the execution time showed that: Local launch `make test` on SSD was sped up by 20% #827 Long 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 for `make test` is 35s. Two parallel `make 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

fyrchik closed this issue

2024-02-12 06:28:01 +00:00

fyrchik reopened this issue

2024-02-12 06:28:10 +00:00

fyrchik modified the milestone from v0.38.0 to v0.39.0

2024-02-12 06:28:13 +00:00

fyrchik modified the milestone from v0.39.0 to v0.40.0

2024-05-14 14:11:43 +00:00

fyrchik modified the milestone from v0.40.0 to v0.39.0

2024-05-14 14:12:01 +00:00

fyrchik added the

internal