Performance on C2D?

[mk]

Hi. I was hoping someone could explain weird performance anomaly. I ran a
small test to compare a new X6800 Core 2 Duo build against a three year old
P4EE:
(Both machines running VS2005)

DateTime dt = DateTime.Now;
string s = String.Empty;
for (int i = 0; i < 9999; i++)
{
s += new string('x', 1000);
}
TimeSpan ts = DateTime.Now - dt;
double l = ts.TotalSeconds;

As you can see its very basic, meant to push memory and cpu activities. On
the older PC this evalutes in approximately 200 seconds. On the newer one,
it takes between 800 and 850 seconds.

Super PI (32m) takes 42m01s on the older machine, and 18m13s on the new one.
The new machine should be three to four times faster in general ops (super
pi is single threaded). I'm assuming that this is an anomaly in .net, which
is unfortunate as the new machine is a development build. Any ideas would be
greatly appreciated.

Thanks

mk

[mk]

Running a new test with just 999 cycles the new machine took 1.06 seconds,
the old machine took 2.22 seconds.

"mk" wrote:

Hi. I was hoping someone could explain weird performance anomaly. I ran a
small test to compare a new X6800 Core 2 Duo build against a three year old
P4EE:
(Both machines running VS2005)

DateTime dt = DateTime.Now;
string s = String.Empty;
for (int i = 0; i < 9999; i++)
{
s += new string('x', 1000);
}
TimeSpan ts = DateTime.Now - dt;
double l = ts.TotalSeconds;

As you can see its very basic, meant to push memory and cpu activities. On
the older PC this evalutes in approximately 200 seconds. On the newer one,
it takes between 800 and 850 seconds.

Super PI (32m) takes 42m01s on the older machine, and 18m13s on the new one.
The new machine should be three to four times faster in general ops (super
pi is single threaded). I'm assuming that this is an anomaly in .net, which
is unfortunate as the new machine is a development build. Any ideas would be
greatly appreciated.

Thanks

mk

[Gabriel Lozano-Morán]

This doesn't answer your question but why don't you use the
System.Diagnostics.Stopwatch?

Gabriel

"mk" <[e-mail] in message
news:58**********************************@microsof t.com...

Hi. I was hoping someone could explain weird performance anomaly. I ran
a
small test to compare a new X6800 Core 2 Duo build against a three year
old
P4EE:
(Both machines running VS2005)

DateTime dt = DateTime.Now;
string s = String.Empty;
for (int i = 0; i < 9999; i++)
{
s += new string('x', 1000);
}
TimeSpan ts = DateTime.Now - dt;
double l = ts.TotalSeconds;

As you can see its very basic, meant to push memory and cpu activities.
On
the older PC this evalutes in approximately 200 seconds. On the newer
one,
it takes between 800 and 850 seconds.

Super PI (32m) takes 42m01s on the older machine, and 18m13s on the new
one.
The new machine should be three to four times faster in general ops (super
pi is single threaded). I'm assuming that this is an anomaly in .net,
which
is unfortunate as the new machine is a development build. Any ideas would
be
greatly appreciated.

Thanks

mk

[mk]

I don't think the problem is with .Net, it appears to be windows-based.
Executing memtest on the old machine works just fine, on my new machine
memtest reports that windows will not allow large contiguous allocation of
memory to a single machine - this forces me to run two instanes of memtest.
In itself this is not a problem, but it shows some underlying issues.
Does anyone know if this is due to installing xp pro with sp2, rather than
xp pro and then sp2 afterwards?

"Gabriel Lozano-Morán" wrote:

This doesn't answer your question but why don't you use the
System.Diagnostics.Stopwatch?

Gabriel

"mk" <[e-mail] in message
news:58**********************************@microsof t.com...

Hi. I was hoping someone could explain weird performance anomaly. I ran
a
small test to compare a new X6800 Core 2 Duo build against a three year
old
P4EE:
(Both machines running VS2005)

DateTime dt = DateTime.Now;
string s = String.Empty;
for (int i = 0; i < 9999; i++)
{
s += new string('x', 1000);
}
TimeSpan ts = DateTime.Now - dt;
double l = ts.TotalSeconds;

As you can see its very basic, meant to push memory and cpu activities.
On
the older PC this evalutes in approximately 200 seconds. On the newer
one,
it takes between 800 and 850 seconds.

Super PI (32m) takes 42m01s on the older machine, and 18m13s on the new
one.
The new machine should be three to four times faster in general ops (super
pi is single threaded). I'm assuming that this is an anomaly in .net,
which
is unfortunate as the new machine is a development build. Any ideas would
be
greatly appreciated.

Thanks

mk