There's a certain amount of controversy over running cadence (or biking cadence for that matter). The typical arguments for it are that it shortens your stride, decreases heel impact, reduces knee injuries and results in a more efficient stride. Some people agree, some think it's a bunch of bananas. I'm not gonna get into it. I will simply can say that faster songs help me on training runs. (I never race with music.) They keep me distracted, give me energy and sometimes push me more than I would have on my own.
So... If you're interested, I've found 2 tricks to making running mixes at a fast bpm. The
Alternatively, you can make your own mixes. I use MixMeister to analyze the bpm of my music, but there are a lot of programs out there. Keep in mind that MixMeister doesn't work for .m4a audio files. For those files, you can use a "tapper" program like WinBPM (I've never used that program, so I'm not sure how good it is. It's just an example.) and manually "tap" out the beat of a song. Not the most efficient, but it works if you have a song or two you think are in the right range and want to confirm.
Another easy way is to simply google "180 bpm music," for example. You'll find that many people have already posted lists of songs at different bpms so you can piggy back of their hard work and use it as a guide for mixes. Remember that songs at half the bpm work as well. If the bpm is listed as "90," it'll work for a 180 cadence. The beat will match each strike for one foot, rather than with each step. For example, you can match your left foot hitting the ground with the beat, as opposed to the beat matching when both your left and right foot strike.
My gift to you is a song I've been rocking to on runs recently. And, yes... it's at 180 bpm.
May the fast be with you!