Hi JC...watching the resource usage on the 3500k AD, it is running about 2.8GB (for the whole machine, not sure about the pwdump processes) memory but very consistent onces it gets going...it has small dips now and then of about 100-200Mb. CPU usage is variable but never high. LSASS process is using about 1.8GB ram. On this 32 bit machine, it could be bumping into some 32bit limits, as an array of about 1 million users is already maybe 320MB...(I think the USERINFO array is 320bytes/record). I'm just wondering about running it remotely (my host machine is 64bit)...so I could compile up the 64bit version of pwdump and run it there...maybe that would help?? On the smaller AD's, resource usage is much lower... I am using pwdump 2.0 beta... I guess I could go back to one of the older versions and try...just it's a long turnaround for each test....7-8 hours! Although I don't have any exact timings, to the eye it seems that it gets slower and slower (based on the output lines/minute) as it progresses, which seems to indicate it's dealing with bigger and bigger things in possibly a less than optimal way somewhere? My c/c++ skills are not good enough to see where this might be...so I don't mean to insult the great efforts that have already been made...after all is seems nobody had run it on an AD > 250k users....so I'm asking lots more of it!!! And I really appreciate all the help I'm getting!! Keith > JC Ferguson wrote: > I cannot recall - is pwdump caching the results locally? I seem to recall some versions doing that. I.e., it builds up all the data in memory, then dumps to a file. If that is the case, I can see some scale issues with 3.5 million entries in your AD, i.e., you'd eat up the memory. When it is chugging along, have you run taskmgr, sort by memory usage, and observed who the hogs were? -jc > -----Original Message----- > From: foofus-tools-bounces@lists.foofus.net [mailto:foofus-tools- > bounces@lists.foofus.net] On Behalf Of Keith Morrell > Sent: Saturday, May 22, 2010 18:52 > To: foofus-tools@lists.foofus.net > Subject: [foofus-tools] pwdump > > Update: I've tried the suggestions from others in the forum and they don't > seem to make a huge difference....but the one remaining issue is still > happening. > > On my ~3,500k AD, the program seems to die about 2.2M records through (2676 > dots), using a very rough estimate of the number of dots displayed on the > screen/time run (from this bit of code in pwdump.cpp) - comparing this to my > ~700k which displayed 851 dots... > > else if(i % 100 == 99) > fprintf(stderr, "."); > > So it seems it must be running out of time or space somewhere... > > When it stops, the {GUID} service is still left running. > > I can compile it all up now to make any other changes others might suggest. > What would be good is a trace output maybe in LsaExt.c, or even some way of > breaking the process up so that the extract (absolute minimum needed) is > done to a "raw" intermediate file, and the final conversion/formatting done > with another module?? > > Thanks in advance for any more help... > > Keith > > > _______________________________________________ > foofus-tools mailing list > foofus-tools@lists.foofus.net > http://lists.foofus.net/listinfo.cgi/foofus-tools-foofus.net