fix: correct statement about execution time(Event loop) #3422
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.
fix: correct statement about execution time(Event loop)
Current text:
The notable thing is that both variants -- with and without splitting the job by
setTimeout
-- are comparable in speed. There's not much difference in the overall counting time.Actual behaviour:
The execution time increases when using setTimeout. ~1.5secs without and ~8secs with setTimeout(desktop). ~3.5secs without and ~15secs with setTimeout(mobile). After the scheduling improvement, the setTimeout variant takes ~4secs(desktop and mobile)
chore: improvement in starting sentence grammar