-
Notifications
You must be signed in to change notification settings - Fork 509
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
PR test in mdn/translated-content is slower than before #8301
Comments
This changes the `findAll()` function to an asynchronous function to help improve performance. Partial fix to mdn#8301.
Please note that individual workflow runs are not necessarily comparable, as workflow runners use a variety of CPUs. |
Sorry about ignoring that, I just made a local test, and found that:
use
use
Test platform:
|
I compared
|
On bf23810, I ran
The time spent gathering all the translations is definitely quite high, I wonder what's causing the sudden change in build times, hmm... |
In v2.5.5 (the latest as of this comment) on a brand new package and folder made specifically for testing Yari, I found that the time spent went down significantly to ~4.3s:
And in v1.36.4, I get around the same time. When I was trying to dig into profiling and performance, I ran a profiler through Chrome's debug panel (within Yari, using the latest branch), and I found something interesting: I don't see much of a reason that the |
After the fix (#8806) is applied, the build time is reduced to |
Summary
I just notice that after we migrating to ESM. The PR test workflow in translated-content is slower that before.
See the following workflow run:
As @queengooborg mentioned in translated-content, maybe we need synchronous file reading for this step.
URL
None
Reproduction steps
See workflow run.
Expected behavior
The workflow could run faster (maybe we could start from the gather translation step).
Actual behavior
The workflow is a bit slow.
Device
Desktop
Browser
Chrome
Browser version
Stable
Operating system
Linux
Screenshot
No response
Anything else?
No response
Validations
The text was updated successfully, but these errors were encountered: