I have started Netmap for Windows and it's rarely using system ressources (e.g CPU-time: 0:00:00, 1MB Memory, very few ip packets over internet connection).
This would be no problem at all if Netmap would find nodes much faster but it doesn't. In 5 hours it only found 340 nodes. How can I speed up this search. Or does the program itself limit the amount of used bandwidth, CPU-time...?
Thanks for you reply
|Well I've just got 125 nodes in well under 5 minutes running it here, though this is starting off, and it will get a bit slower as it continues.|
One reason for slight slowness is that although I think it sends and receives the ping packets of different lengths out in parallel, it does DNS lookups on any new hosts found in serial. Still I'd expect it to go a bit faster than you're describing.
You can actually run many instances of netmap.exe to get it to go faster - or at least, I _think_ you can. I certainly wrote a multithreaded driver for it at one stage, but it caused an alert at Oxford's computer security centre because there were too many ping packets! The multithreaded one got >50000 hosts in a few days.
Today's weather in %region is Sunny/(null), max. temperature -99999°C
I'll try running many instances over the next few days
|In about an hour I got 2000 nodes, the net view makes absaloutly no scence tho, lots of bit all over none seem to all be connected just little random bits floating around :/, be good if it all origonated from "you" like a spider web rather then little bits floating around.|