I am no expert, but it sounds like LOADDB is a single threaded process. It jus plain does not take advantage of multiple processors. I guess that if we look, it is not spawning any child tasks to do multithreading nor is it multithreading internally either (the two main ways I know of that folks take advantage of multi-processor systems).
> -----Original Message----- > From: Rushforth, Tim [SMTP:[EMAIL PROTECTED]] > Sent: Friday, March 22, 2002 2:23 PM > To: [EMAIL PROTECTED] > Subject: DSMSERV LOADDB with 2 processors > > We've been doing some loaddb testing and have found that when we add a > second processor (Intel PIII 1 Ghz) the loaddb takes nearly twice as long > to > run. > > The loaded DB resulted in about 17GB being used. > > Auditdb took about the same amount of time to run with 2 processors as > with > 1. > > Tested with TSM 4.2.0.0 and 4.2.1.11 on W2K. > > With 4.2.0.0 the load took 1hr 50 min with 1 processor, 3hr 44 min with 2 > processors. > > Withe 4.2.1.11 the load took 2hr 44m with 1 processor, 4hr 45 min with 2 > processors. > > All of the loads were done from the same unloaded db. > > CPU utilization with one processor was constantly near 100%, with 2 > processors each was running around 50%. > > Has anyone ever come across this? > > Does this seem like a bug in loaddb? > > Thanks, > > Tim Rushforth > City of Winnipeg
