I'm sorry, but how? You'd need data centers worth of effort for many years.
(I should say I'm not a professional security engineer so I'm probably wrong about everything and would appreciate corrections. )
Just want to tack on one footnote: 100 ms is based on a single CPU core. Most CPUs have 4-8 cores. So instead of 10 passwords a second you could argue 40-80 passwords a second is believable with concurrent operations (which all popular hash cracking software supports).
It is definitely viable to break a single user's hashed password no matter what the scheme or work factor. Strong hashing algorithms with high work factors just stop you breaking multiple user's passwords quickly (and gives you 1-3 days of delay). It is a stop gap, not impenetrable defence like some believe.
All technical people need to take a day and learn how to break password hashes. Not just the theory, but go download the software and actually do it.
And now that hashcat and oclhashcat have merged[1] and are open-source[2] it's never been easier to install hashcat and start cracking passwords!
[1] https://hashcat.net/forum/thread-5559.html [2] https://hashcat.net/forum/thread-4880.html
If you are not using salt, you are vulnerable to rainbow attacks within the same database.
Using pepper prevents that from happening, and storing it separately from your database makes it much harder to get both.