Most of the benefit from this approach would come if you can often expect streams of 16 bytes to contain no white space character. This seems like a good guess in many applications.
<a href="https://lobste.rs/s/fajid3/pruning_spaces_from_strings_quickly_on">Pruning spaces from strings</a> has 80 consecutive bytes of non-whitespace, which is 4 or 5 chunks depending on how it ends up aligned.
Sounds quite unlikely to me.
<a href="https://lobste.rs/s/fajid3/pruning_spaces_from_strings_quickly_on">Pruning spaces from strings</a>has 80 consecutive bytes of non-whitespace, which is 4 or 5 chunks depending on how it ends up aligned.