Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.1
-
Fix Version/s: 5.0.4
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any with image io and jai
Description
The file in question located on Support drive under /9361. The file take quite a lot of CPU time to decode the images in question. This bug is a placeholder so we can revisit for any potential optimization.
Activity
Patrick Corless
created issue -
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Workaround Description | Pushing to next release. | |
Salesforce Case | [] | |
Fix Version/s | 4.3 [ 10266 ] |
Patrick Corless
made changes -
Workaround Description | Pushing to next release. | |
Salesforce Case | [] | |
Fix Version/s | 5.0 [ 10314 ] | |
Fix Version/s | 4.3 [ 10266 ] |
Patrick Corless
made changes -
Fix Version/s | 5.0.1 [ 10872 ] | |
Fix Version/s | 5.0 [ 10314 ] |
Patrick Corless
made changes -
Fix Version/s | 5.1 [ 10675 ] | |
Fix Version/s | 5.0.1 [ 10872 ] |
Patrick Corless
made changes -
Fix Version/s | 5.0.4 [ 11072 ] | |
Fix Version/s | 5.1 [ 10675 ] |
Patrick Corless
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Patrick Corless
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Most of our image decoding slow down is related to how we go about converting the image data to RGB. There are a couple different ways we can improve the load time. The first easy optimization would be to avoid getting a pixel at a time, it is possible to copy a whole row of image data into an array which is supposed to be quite a bit faster.
The other optimization is to move image loading to into separate thread or at the very least delay it until paint time. A separate image loading thread would improve the user experience greatly even if the today decode time didn't improve. The content parser will stall on a large image effectively blocking the display of page content until the image is loaded. If we started painting the main text content first and repainted later for a image done event the rendering core would seem a lot faster.