To use your own locally cached symbols (which you may have in your _NT_SYMBOL_PATH, for "srv*c:\websymbols*http://msdl.microsoft.com/downloads/symbols" it is c:\websymbols), you can use the junction:
mklink /j Symbols c:\path_to_your_symbols
(mklink /j Symbols c:\websymbols)
where Symbols is the subdirectory of the directory containing dumpinterpreter.exe.
The version of the app with changes made yesterday is in the attachment to this post. I tried different sets of .dmps and for 100 dumps the time of full analysis ( ".reload, !analyze -v, r, kv, lmtn, lmtsmn, .bugcheck, !peb, !sysinfo machineid, !sysinfo cpuspeed, !sysinfo smbios") is ~75 secs (so, less than a second for one .dmp file, for next runs it is close to 0.5 sec/dump). The analysis time differs from dump to dump and usage of multiple threads helps in optimizing the total time of the analysis - one dump doesn't stop entire process and total time is not just a sum of timings, so the number of threads can be 10 for one or two core systems (with multithreading) and more for other (20 threads is just ok for my quad core - so 8 logical processors). As I mentioned before, the analysis takes lot of I/O time, so I don't feel that my system is busy. Cdb.exe uses ~50-70 MB for every dump and dumpinterpreter.exe uses ~0.4GB for analysis with 20 running threads (about 20MB for one thread).
Did you try to make some changes to your app regarding symbol paths?
m.g.
