I have no idea how I'm going to make nmap faster yet. It's taking about 3-5hrs to chew through the 3k+ hosts we need monitored now, which is nice enough, I guess, but it's still painfully slow atm.
Firing off multiple instances seemed to work, but I'm not sure if that negatively impacted accuracy. Even forcing batches of 128 hosts took at least 20min per batch to finish. Something's slowing down the processing, and I'm not entirely sure what. Maybe I need dtrace...
@smallsees I'm running it with input from a file and logging to a file, so there shouldn't be any I/O bottlenecks unless ZFS is too slow on some SSDs, which seems unlikely. At this time, the most likely candidate seems to be `-Pn`, but I can't trust ping scans to validate targets, so I need to find out where things are slowing down and what can be done to work around it.
@omnipotens That's pretty awesome, but I can't rely on pings to verify a host is alive, so I've been working with the ttl timing options to skip hosts if they don't respond within a reasonable window. Might be able to reduce that window some, but I feel like there's something else that I'm missing that can cut down on this latency.