docs: the rayon fix covers a one-thread pool, not the h5py-process gap

The review measured the default pool unchanged (about 2900 MB/s at 16 threads before and after) and still short of 16 h5py processes; small pools still make outside readers wait. Say so instead of marking the scaling issue fixed. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-26 08:48:05 -05:00
parent a5e41c1a53
commit 37770f594a
3 changed files with 14 additions and 9 deletions
@@ -13,7 +13,8 @@
  (`clawhdf5_format::parallel_read::pool_can_parallelise`). The `File`'s
  chunk cache, the suspect in `docs/known-issues.md`, was not the cause:
  reads of datasets larger than its budget already skipped inserting, and
-  its lookups cost a few percent at 16 threads.
+  its lookups cost a few percent at 16 threads. Throughput with the default
+  pool is unchanged, and still short of an h5py process pool.

 ### Plugin filters (2026-09-26)
 - **LZF, bitshuffle, bzip2 and Blosc read and write, in pure Rust.** Files