|Perl: the Markov chain saw|
Re^2: Program Design Around Threadsby aeaton1843 (Acolyte)
|on Mar 06, 2013 at 18:15 UTC||Need Help??|
I wanted to answer your questions. I will have to run through the proposed solution tonight.
1. It depends but 2-3k, maybe less if I can narrow to a specific data center.
2a. I am being careful with thread bombing the proxy. I have a thread creation limitter. Right now it is sitting at 10 threads.
2b. Worst case, I have to pull an entire configuration off an Arista. That process can take 30 seconds on a busy Arista device. Much less for most everything else.
3. I think the worst case is "show interface" @ 20ish*384/per machine The 20ish is variable based on what is configured on the interface. Traffic shaping for example.
4. Sorry I wasn't clear enough here. I want one file per queried machine with all of the command outputs in it.
5. The outputs of each command should be put into the output file in the order of the command list in the command file. IE if show running-configuration is first in the command file then its output should appear first in the output file. Not that it matters but right now the file's name is that of the machine name.