You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we verify all the links with a variation of mapConcurrently.
Given that local links checking is a pure action, we could use something lighter for them.
But this is debatable, we will have to try and see how much do we win in practice and whether is the improvement worth the increased complexity.
Limits
If an application can exploit many cores, usually it does not consume all the cores by default and the application provides -j flag for increasing the number of used OS threads.
However, in this case this is probably redundant? Even if the repository contains like 100 .md files, the overall amount of computations should not be larger than several seconds. If we exploit all the cores, that should be a large load for a very short duration.
And actually, I/O likely will dilute the computation part.
Clarification and motivation
Let's take a thorough look at how concurrency is used here.
Acceptance criteria
The text was updated successfully, but these errors were encountered: