My goal: I want to ping every single IPv4 address and record whether or not they responded.

The way I have it set up is every IP address corresponds to an index. For example is index 0 and is index 256. So if responded, then the 0th element of the bitarray is true. At the end I write the bitarray to a file.

Here is the code:

import subprocess
from bitarray import bitarray
import threading
import time

response_array = bitarray(256 * 256 * 256 * 256)

def send_all_pings():
    index = 0
    for f1 in range(256):
        for f2 in range(256):
            for f3 in range(256):
                for f4 in range(256):
                    thread = PingerThread(".".join(map(str, [f1, f2, f3, f4])), index)
                    index += 1

    print("Writing response array to file")
    with open('responses.bin', 'wb') as out:

class PingerThread(threading.Thread):
    def __init__(self, address, index):
        self.address = address
        self.index = index

    def run(self):
        if["ping", "-c", "1", "-w", "1", self.address]) == 0:
            response_array[self.index] = True
            response_array[self.index] = False

What can I do to make this run faster? Any optimisations at all, even if very small, are welcome!

Opening four billion network connections potentially at once doesn't sound like a good idea. I can't tell right now whether or not you'll hit the OS limit and if it will be handled in some graceful way like blocking until a handle is free, but I'd rather set up a sane limit up front.

Some suggestions:

  • IP addresses are only formatted as octets (0-255) for human readability - they actually just represent integers. Instead of for example you can use 2130706433 (127*2^24+1). In other words, range(2^32-1) represents the entire range of IPv4 addresses.
  • Using a Python library to ping hosts is very likely going to be much faster than starting a shell command.
  • Use multiprocessing rather than Python threads to avoid running into the global interpreter lock
  • response_array will end up taking many gigabytes of memory. If you really need the kind of detail you're logging you should be writing each entry to disk ASAP (keeping the file open all the while). You could also look into simplifying your reporting, such as only saving the IP addresses which don't respond, or saving to two files, one with responding IPs and the other with non-responding ones. You'll have to store a file (or a pair of files) per process, to avoid them clobbering each other.
  • 1
    Since this is mostly waiting on a network, async io might be even better than multiprocessing. Although you probably don't want 4 billion open connections, but that's an issue with the original code as well – millimoose Dec 7 at 0:51
  • Also saving to two files from umpty concurrent processes sounds like either a bottleneck or a way to end up with a file full of garbage. – millimoose Dec 7 at 0:56

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.