arhammusheerandClaude Opus 5.5 f8064ba3ce #1172: rasterize with up to 8 threads instead of 4 ...

The automatic rasterizer thread count was one per core up to 4. On a 10-core Apple M2 Pro, 8
workers are faster (9 are slower again), and vello_cpu draws the same pixels with any number:

- fit page, 50,000 paths: 66.7 → 56.6 ms; after a pan 66.4 → 51.2 ms
- 400 % zoom, 50,000 paths: 17.8 → 15.7 ms (back under its 16 ms budget)
- fit page, 100,000 paths: 137 → 105 ms; 400 % zoom 33.0 → 25.8 ms

Machines with 5 cores or fewer keep their count, and Preferences → Performance and
VECTORCRAFT_RENDER_THREADS still override it. pixels_do_not_depend_on_the_thread_count renders
a page of live effects and 400 overlapping translucent objects with 0, 1, 4 and 8 workers and
gets the same pixels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VmMmc1J8XeNLxhRihWv9cc

2026-10-11 23:26:53 +07:00

..

examples

Robustness: VectorCraft never crashes — no panics in shipped code

2026-10-05 06:28:59 +07:00

src

#1172: rasterize with up to 8 threads instead of 4

2026-10-11 23:26:53 +07:00

tests

Render: a shape far beyond any page is left undrawn, never crashing the app

2026-10-11 16:13:30 +07:00

Cargo.toml

M4.70: PSD export, flat or with layers, groups for sublayers and text layers named after their text

2026-10-05 16:12:03 +07:00