Skip to content

Take the jpeg2000 release that stops holding a page in the colour transform - #96

Merged
tannevaled merged 1 commit into
mainfrom
bump-jpeg2000-v0111
Sep 28, 2026
Merged

tannevaled merged 1 commit into
mainfrom
bump-jpeg2000-v0111

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

go-images/jpeg2000 v0.11.1 runs the inverse ICT a band of 64 rows at a
time. Its six pooled SIMD images were the size of the page — six float64
planes is 48 bytes a pixel — and InverseICT is pixel-wise, so the rows held at
a time were free to choose all along.

Decoding one 4559×6942 three-component scan and nothing else, so the figures are
the decoder's:

peak RSS live heap
v0.11.0 2416 MB 1208 MB
v0.11.1 990 MB 741 MB

45% of the measured corpus is three-component — 54 130 of 119 164 JPEG 2000
streams — so this is not a corner. A colour page cost six times a grey one per
pixel before this.

Nothing in this repository changes. All 3215 documents of the measured corpus
render byte-identically (0 different, 66 drawn by neither, population floor
3000), rendered by exactly this pair, and the module in the cache was diffed
against the tree that was proved.

Speed is not claimed: the machine was carrying two system daemons at 132% and
86% of a core, and a timing taken under that describes the daemons.

🤖 Generated with Claude Code

…nsform

v0.11.1 runs the inverse ICT a band of 64 rows at a time. Its six pooled SIMD
images were the size of the page -- six float64 planes, 48 bytes a pixel -- and
InverseICT is pixel-wise, so the rows held at a time were free to choose all
along.

On a 4559 by 6942 colour scan, decoded alone, peak RSS falls 2416 -> 990 MB and
the live heap 1208 -> 741 MB. 45% of the measured corpus is three-component, so
this is not a corner.

Nothing here changes: all 3215 documents of the measured corpus render
byte-identically, rendered by exactly this pair.
@tannevaled
tannevaled merged commit db882c8 into main Sep 28, 2026
9 checks passed
@tannevaled
tannevaled deleted the bump-jpeg2000-v0111 branch September 28, 2026 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant