SEARCH
diglloydTools™
|
|
|
|
|
2022 MacBook Pro M2 Max: IntegrityChecker Java, Verify
Related: 2019 iMac 5K, 2019 Mac Pro, 4K and 5K display, Apple MacBook Pro M2, Apple Silicon, computer display, data integrity, diglloydTools, iMac, iMac 5K, IntegrityChecker, Java, laptop, Mac Pro, MacBook, MacBook Pro, Macs, Other World Computing, SSD
Please buy your gear at B&H Photo and OWC/MacSales.com using any link from this site.
Consult with Lloyd, to design a complete system for photography or similar including backup and data safety
MPG tested the Apple 16.2" MacBook Pro with M2 Max Chip Z1740017Z, maxed-out excepting 4TB SSD.
About
Cross-platform (any computer with Java), IntegrityChecker Java runs SHA512 hashes on files to maintain data integrity checks. All professionals should be using it to validate their data. Especially when random “land mine” bugs in new macOS releases pop up, such as macOS Finder silent data-loss risks and outright bugs when copying files.
Or bad memory or bit rot (rare but real), etc.
The verify command of diglloydTools IntegrityChecker utilizes all CPU cores as efficiently as any application ever can, using sophisticated I/O algorithms to feed data to the CPU as fast as the OS can go. Performance will thus be gated by I/O speed unless all CPU cores are fed data fast enough to be fully utilized.
If below are out of date: view current Mac wishlist and all current OWC wishlists.
Results
The 2019 Mac Pro can hash at 12+ GB/sec on a faster SSD, but its results as shown here are on its Apple internal SSD, which maxes-out at ~3.4GB/sec.
The 2022 MacBook Pro M2 Max is limited not by its SSD, but by its CPU speed, which happens to max-out at about half its SSD speed. This stems from the lack of specialized CPU instructions for cryptographic hashing. Fast enough? Yes, for most all users. But way below what the SSD allows for. See the next graph where I/O speed is much faster.
The M1 Max takes about 21% longer than the M2 Max.
When originally tested, the M1 Max did 5% faster than shown here (2746 MB/sec vs 2606 MB/sec). The file set did change somewhat so that might explain it.
With cached data (I/O a minimized factor), the picture changes to show the CPU capability, where the Intel Macs easily outperform.
