Tweeeek
Wed Nov 12 03:56:50 CST 2003
Hi
Thanks for all the responses;
The spec of the machine is as follows
1)M/Board MSI K7D Master (supports 64 bit PCI)
2) CPU AMD AthlonMP PR2400+ (I will have these in the next day or so) I
couldn't wait so I bought some cheap AMD Duron 1.4Ghz Socket A (266Mhz FSB)
and converted them to MP by bridging L5, these are now recognised by the
M/BOARD and XP as MPs
3) 512MB of registered RAM
4) Adpatec 29160(64 bit pci) SCSI controller card (160 MByte/sec)
5) 18GB SCSI 10,000 rpm (IBM DDYS-T18350N). I have installed Windows XP
Professional on this and my other Applications, and part of platform builder
4.2
6) 36GB SCSI 15,000 rpm (Maxtor Atlas15K_36WLS), when I installed platform
builder 4.2 I installed the WINCE420 portion on to this drive. This is the
only thing on this drive and I thought this was the
optimum configuration
7) I also have an IDE drive, which I use for genral storage
a) With only a single processor running, I start a build and use the
performance monitor I see that the processor are running 100 percent which
is expected since they are only cut down versions
b) With two processors running but BUILD_MULTIPROCESSOR =, this gives
bldMP=, BUILDING with __bldMP=, the performance monitor shows two processors
running at
50% which is what I expected
c) With two processors running but BUILD_MULTIPROCESSOR =1, this gives
bldMP=2, BUILDING with __bldMP=-M 2, the performance monitor shows two
processors running at
about 100% which is what I expected, but it only reduces the build time
by three minutes.
Somethings wrong somewhere, it feels as though its not using the dual
processors correctly, and basically spawns two threads and runs them on the
same processor. During the build process with the with BUILD_MULTIPROCESSOR
=1, the build screen outputs the files its building (as it always does) but
this time each line has a >1, or >2. Now I don't think this is referring to
the processor being used, since on another machine running a single
processor and platform builder 3 I can set BUILD_DEFAULT=%BUILD_DEFAULT% -M
2 (or even -M 10) and the building screen shows different files being
compiled on different threads, I as it builds I get lines starting with >1,
>4, >9 etc.
I think the build screen processor being used is a red herring.
As mentioned earlier, running with point (b) above for a typical build (with
deptrees enabled) took 23 minutes
Running with point (c) above for a typical build (with deptrees enabled)
took 20 minutes, from the evidence (performance monitor, I take these
results with a pinch of salt) I was expecting a build time of about 10
minutes.
I'm missing something, the documentation on dual processor support is also
poor.
Any help would be appreciated
Regards
Tariq
"Bob" <bob@somewhere.ch> wrote in message
news:%23qxULKPqDHA.2848@TK2MSFTNGP10.phx.gbl...
> We've never seen something similar. Is all of your hardware
> on the HCL for your OS? See:
>
>
http://www.microsoft.com/whdc/hcl/default.mspx
>
> What OS do you use btw? Have you tried, as Steve Maillet
> suggested, to disable antivirus software?
>
> A bad driver to your hard disk controller could be the
> cause. I would guess your hardware is the problem
> more likely than platform builder.
>
> As I understand PB doesn't take more than 180 MB, so
> what is eating memory? Is it some other process? If
> it's kernel memory, a bad driver or antivirus software
> is likely the problem.
>
> Does it happen if you make a completely new platform in
> platform builder using only default values (try "new
> platform", and click next... and rebuild, and see if
> it's something related to your platform only.
>
>
>
>
>
>
>
>
> "sergei" <anonymous@discussions.microsoft.com> wrote
> >
> > >-----Original Message-----
> > >Hi
> > >I h