Add a temporary function-cache in AlternateCS.prototype.getRgbBuffer
#19428
+43
−12
Conversation
This file contains 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
|
/botio test |
From: Bot.io (Linux m4)ReceivedCommand cmd_test from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/7625531251bb676/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_test from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.193.163.58:8877/cac5f481ec59fdc/output.txt |
From: Bot.io (Linux m4)FailedFull output at http://54.241.84.105:8877/7625531251bb676/output.txt Total script time: 29.58 mins
|
Snuffleupagus
force-pushed
the
AlternateCS-getRgbBuffer-tintCache
branch
from
d36ce6c to
40d5b7c
Compare
From: Bot.io (Windows)FailedFull output at http://54.193.163.58:8877/cac5f481ec59fdc/output.txt Total script time: 58.83 mins
|
Snuffleupagus
force-pushed
the
AlternateCS-getRgbBuffer-tintCache
branch
3 times, most recently
from
648e0af to
47c9a21
Compare
This supplements, rather than replaces, the existing caching in `PDFFunction.constructPostScript` since that one still makes sense given that functions are cached on the page-level. Using an additional cache helps improve performance because: - There are many fewer function calls, and overall less parsing this way. - For the common case of `Uint8Array`-data we're able to use integer cache-keys, which is a lot faster than string concatenation. This significantly improves performance of the `pr5134` test-case with `isEvalSupported = false` set, and testing locally in the viewer: - With the `master` branch and `isEvalSupported = true`, page 2 renders in approx. 340 milliseconds. - With the `master` branch and `isEvalSupported = false`, page 2 renders in approx. 1200 milliseconds. - With this patch and `isEvalSupported = false`, page 2 renders in approx. 380 milliseconds. While this is obviously still slower, the difference is now small enough that it shouldn't be too much of an issue in practice (compare with PR 18070) and the `pr5134` test-case is an especially "bad" one w.r.t. its PostScript function use.
Snuffleupagus
force-pushed
the
AlternateCS-getRgbBuffer-tintCache
branch
from
47c9a21 to
adfc49c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This supplements, rather than replaces, the existing caching in
PDFFunction.constructPostScriptsince that one still makes sense given that functions are cached on the page-level.Using an additional cache helps improve performance because:
There are many fewer function calls, and overall less parsing this way.
For the common case of
Uint8Array-data we're able to use integer cache-keys, which is a lot faster than string concatenation.This significantly improves performance of the
pr5134test-case withisEvalSupported = falseset, and testing locally in the viewer:With the
masterbranch andisEvalSupported = true, page 2 renders in approx. 340 milliseconds.With the
masterbranch andisEvalSupported = false, page 2 renders in approx. 1200 milliseconds.With this patch and
isEvalSupported = false, page 2 renders in approx. 380 milliseconds.While this is obviously still slower, the difference is now small enough that it shouldn't be too much of an issue in practice (compare with PR #18070) and the
pr5134test-case is an especially "bad" one w.r.t. its PostScript function use.