It ain't about the amount of commit, neither the amount of line changes, it's about how much of business and functional logic your commit have.
I mean, I can make 20 commits per day, but at the end, someone who reviews my history line don't get nothing from it.
Atomic commit are meant to bring the history of the development, that's something that not everyone knows how to do, how to read code and understand it. It's very easy to understand some logic if the commits give me the 'description' of a class by instance.
So, at the end, it ain't just about the amount of commit, it's about how rich they are, amount of changes, what they bring to the business logic, features (which HAVE to be atomic) ...
It's quiet difficult to see a project manager or team leader to use the real power of metrics....