compile/action: start with a build using setscene only#2004
Draft
Jose Quaresma (quaresmajose) wants to merge 1 commit into
Draft
compile/action: start with a build using setscene only#2004Jose Quaresma (quaresmajose) wants to merge 1 commit into
Jose Quaresma (quaresmajose) wants to merge 1 commit into
Conversation
Contributor
Author
|
Initial tests suggest that the NFS latency is negligible:
|
|
This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time. |
Contributor
Author
|
Revisit after #2195 |
Jose Quaresma (quaresmajose)
force-pushed
the
setscene-only
branch
from
1114f21 to
d909a2f
Compare
Test Results 25 files - 41 25 suites - 292 52m 25s ⏱️ - 2h 58m 27s Results for commit 71578f2. ± Comparison against base commit 93a30e0. This pull request removes 142 tests.♻️ This comment has been updated with latest results. |
Jose Quaresma (quaresmajose)
force-pushed
the
setscene-only
branch
4 times, most recently
from
57550af to
3428102
Compare
Since the sstate-cache used in CI is hosted on a NFS server, this change will allow measuring its latency. Performing an initial build at each subbuild step using only the bitbake setscene tasks, will allow us to measure the time of that task. Which basically consists of executing all the task that can be accelerated using the stored sstate-cache. These tasks make exhaustive use of the NFS filesystem to acquire the sstate-cache artifacts. With this change, it will be easy to distinguish between the time required to acquire and unpack the sstate-cache artifacts and the time spent on the build itself. Signed-off-by: Jose Quaresma <jose.quaresma@oss.qualcomm.com>
Jose Quaresma (quaresmajose)
force-pushed
the
setscene-only
branch
from
3428102 to
71578f2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since the sstate-cache used in CI is hosted on a NFS server, this change will allow measuring its latency.
Performing an initial build at each subbuild step using only the bitbake setscene tasks, will allow us to measure the time of that task. Which basically consists of executing all the task that can be accelerated using the stored sstate-cache. These tasks make exhaustive use of the NFS filesystem to acquire the sstate-cache artifacts.
With this change, it will be easy to distinguish between the time required to acquire and unpack the sstate-cache artifacts and the time spent on the build itself.