I don't know why you added all those numbers. Running the following trims all snapshots:
sudo tmutil thinlocalsnapshots /
Also wouldn't recommend using Onyx to mess with snapshots as they are handled by tmutil and if you use some third party tool to wipe them, the service won't know that occurred, which could lead to corruption or failures in backups down the line.
Moreover, the local snapshots, while they show up as "data' aren't really data. The snapshots are hardlinks, and apfs is really advanced in how it handles shadow copies and links in general. Which makes the system data reports unreliable at best.
Additionally, snapshots and other data no longer needed (sometimes deleting files doesn't actually delete them physically) aren't removed right away to increase the longevity of your drive, but rather on demand. Wiping them out manually just stresses your SSD needlessly and kind of cobbles apfs' more advanced functionality.
We all can see that indeed you do not know why those numbers were included. I found that "sudo tmutil thinlocalsnapshots /" command here on MacRumors, with the explanation:
"Delete all local snapshots at once"
Code:
sudo tmutil thinlocalsnapshots / 9999999999999999 1
or
sudo tmutil thinlocalsnapshots / 1000000000000000 4
Explanation:
/ = the volume to thin (usually your main drive)
9999999999999999 = an arbitrarily huge number (forces it to purge as much as possible)
1 = urgency flag (1 = immediate) (4 = very urgent)
Your post is contradiction itself, saying sudo tmutil thinlocalsnapshots / is enough and later saying it is not advisable to delete the snapshots at all.
I assume the developers at Oynx know more about that than any of us do, and in actual use over several years, I and others have not seen any bad effects from using sudo tmutil thinlocalsnapshots / (large nimber 1)
If you don't want to use that command, fine, don't....
But using it did save a lot of SSD space for several people.