3 ms·
As in 20% faster on the M2? At least for gzip defaults the per core throughput on my M1 is around 50MBps.
by hedgehog 4y ago
As in 20% faster on the M2? At least for gzip defaults the per core throughput on my M1 is around 50MBps.
- hot_gril 4y agoAs in, possibly slower on the M2. Zipping a complex file tree can be disk-constrained, particularly if there are many small files.
- hedgehog 4y agoFor scale we're talking > 2TBps linear read and probably > 500MBps random 4k read in both cases, compared to on the order of 50-500MBps limit on the CPU side depending on threading etc. So still CPU limited. If there's any problem with big file trees it's probably macOS's relatively slow filesystem so again, advantage to the faster CPU. It sounds like LightRoom startup is a little slower but if you use it for editing you're going to get that back in faster workflow. In general modern NVMe has removed disk as a significant bottleneck for normal peoples' workflows, even on Mac. That includes backups, zipping up collections of files, git compaction, etc. What scenario are you imagining here?