You make statements -- that you must just pluck out of your own imagination -- that simply don't make sense.
Multi-threading this particular program is of doubtful merit, ... Yes, it will be able to overlap doing multiple network pings at one time. That’s the only payoff ...
On a 100Mb/s network, average icmp ping times are around 0.2 milliseconds. The OP is using a 10 second timeout for his pings. In the same time that one thread spends waiting for an unresponsive server to time out; another thread can have successfully pinged 10/0.0002 = 50,000 machines!
And if the OP is on a 1Gb/s or a 10Gb/s or 40Gb/s network ...
Payoff enough I think. But there's more ...
There is no computation to be done here; all of the threads are going to gang-up on the SQL server,
Firstly, WMIC isn't an SQL server. It responds to SQL queries, but there is no separate server involved to "gang-up on".
WMIC is an OS internal -- memory based -- DB; and the code that performs the queries runs in the thread that invokes the query!
In other words, all the computation done to fulfill the query, is done by the calling thread!
You are helping no one with answers that are this far off base.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |