Optimus Prime Optimizes Prime
Hi there folks. Optimus Prime here. Few of you know this, but when I’m not out blowing up bad guys with my ion-blaster and swinging my energon-axe, I enjoy solving Project Euler problems over a bowl of oatmeal and a cup of coffee at breakfast. Weird, right? It’s like seeing your teacher walking out on the street, or bumping in to your shrink at the grocery store. Anyway…
I wanted to talk to you about a piece of a Euler problem that I particularly enjoyed optimizing (the problem itself is here). It’s the method I call is_prime?
, which, as it’s name suggests, checks to see if a given number is prime. Sure, I could use the built in ruby method Prime.prime?(n)
, but where would the fun be in that?
Here’s my first attempt at defining this method. We’re essentially brute-forcing our way through every possible number, returning true
unless one of those numbers ends up dividing without a remainder into n
:
1 2 3 4 5 6 7 8 9 |
|
The optimizations I’ve come up with all have to do with finding ways other than brute force to test the prime-ness of the number. To start, testing for factorization of numbers above one half of a given n
is useless. i.e. 32 can never have a factor (other than itself) above 16. So let’s change the range to one half of the given number:
1 2 3 4 5 6 7 8 9 |
|
Ok, so if we’re checking to see if the number 997 is prime (it is) we’ve now gone from looping 996 times to looping 497 times. A good start.
But if our num
is divisible by 2, why are we still checking divisibility by 4,6,8 and every other even number up to num/2 ? That’s about as silly as Megatron thinking he could win the battle of Autobot city by ordering the Constructicons to merge into the gestalt Devastator. Sheesh.
What to do about this? My solution is to add a break
in the loop if num % n == 0. Once we find that a number is not prime, we can end the loop. It’s redundant to have to continue checking:
1 2 3 4 5 6 7 8 9 10 |
|
Now, if we’re checking to see if the number 1000 is prime, we’ve gone from 999 loops, to 499 loops, to 1 LOOP. We break out of the loop because we see that 1000 % 2 == 0. Amazing.
Our last optimization is one that isn’t so straightforward. In fact, the only reason I know about this one is that I hang around transformers that are way smarter than I am. Here it is: You never have to check for prime factors above the square root of the number you’re looking for. For example, the number 36 will not have any prime factors about its square root, 6. Since 2,3,4 and 6 all factor in to 36 and are less than or equal to it’s square root, 36 is not prime. So if nothing at or under the square root of a number is a factor of the number, then that number has to be prime. We replace optimization #1 with our new optimization here:
1 2 3 4 5 6 7 8 9 10 |
|
Here is a breakdown of iterations for each of our is_prime?
methods:
Number to test | Un-optimized | Optimization 1 | Optimization 2 | Optimization 3 | 20 | 19 | 9 | 1 | 1 |
---|---|---|---|---|
997 | 995 | 497 | 497 | 30 |
1000 | 998 | 499 | 1 | 1 |
5915587277 | 5915587275 | 2957793638 | 2957793638 | 76911 |
Cool, eh? That’s all I have for today. Time to get back to battling the Decepticons.