By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,933 Members | 1,223 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,933 IT Pros & Developers. It's quick & easy.

Performance XP versus W2003S

P: n/a
I have an application written in VB.NET (Visual Studio 2003 and Framework 1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same code
with the same data on a Windows 2003 Server machine it takes over 3 times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any significance.

Has anyone any experience of similar issues? What can cause it and how do
you cure it?
Jun 27 '08 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Strange that no one answered this question until sofar as the answer is
pretty obvious

Your program is written as an application XP gives standard priority to user
applications a server operating system on the other hand is specially
configured to run background services
so all priority is given to background services and not to running
applications

You can do 2 things

1. reconfigure the server so that it will give prio to applications instead
of background services
2. rewrite your program so that it runs in a service context

By the way same thing happens the other way around SQL server , IIS etc etc
responds much faster on a Windows server machine however you can reconfigure
XP to so that it gives prio to background services

Configuration screen , System , Advanced Tab , Top most option

HTH

Michel Posseth [MCP]

"RichG" <Ri***@discussions.microsoft.comschreef in bericht
news:E2**********************************@microsof t.com...
>I have an application written in VB.NET (Visual Studio 2003 and Framework
1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same
code
with the same data on a Windows 2003 Server machine it takes over 3 times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any
significance.

Has anyone any experience of similar issues? What can cause it and how do
you cure it?

Jun 27 '08 #2

P: n/a
Tried changing the configuration but it did not solve the problem. If
anything it made things worse, average time without change 12.1 sec, with
change 12.3 secs.

Any other thoughts?

"Michel Posseth [MCP]" wrote:
Strange that no one answered this question until sofar as the answer is
pretty obvious

Your program is written as an application XP gives standard priority to user
applications a server operating system on the other hand is specially
configured to run background services
so all priority is given to background services and not to running
applications

You can do 2 things

1. reconfigure the server so that it will give prio to applications instead
of background services
2. rewrite your program so that it runs in a service context

By the way same thing happens the other way around SQL server , IIS etc etc
responds much faster on a Windows server machine however you can reconfigure
XP to so that it gives prio to background services

Configuration screen , System , Advanced Tab , Top most option

HTH

Michel Posseth [MCP]

"RichG" <Ri***@discussions.microsoft.comschreef in bericht
news:E2**********************************@microsof t.com...
I have an application written in VB.NET (Visual Studio 2003 and Framework
1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same
code
with the same data on a Windows 2003 Server machine it takes over 3 times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any
significance.

Has anyone any experience of similar issues? What can cause it and how do
you cure it?


Jun 27 '08 #3

P: n/a
Go to Control Panel , System , Advanced , Performance Settings , Advanced

tab. Change Processor scheduling to Programs

and lastly, change Memory usage to Programs. Now click on OK.

On equal hardware , with the same services running with equal load and the
above switches equal to XP, Windows 2003 should outperform Windows XP easy
are you sure the windows 2003 server isn`t running IIS , SQL or whatever on
the background ??

HTH

Michel


"RichG" <Ri***@discussions.microsoft.comschreef in bericht
news:12**********************************@microsof t.com...
Tried changing the configuration but it did not solve the problem. If
anything it made things worse, average time without change 12.1 sec, with
change 12.3 secs.

Any other thoughts?

"Michel Posseth [MCP]" wrote:
>Strange that no one answered this question until sofar as the answer is
pretty obvious

Your program is written as an application XP gives standard priority to
user
applications a server operating system on the other hand is specially
configured to run background services
so all priority is given to background services and not to running
applications

You can do 2 things

1. reconfigure the server so that it will give prio to applications
instead
of background services
2. rewrite your program so that it runs in a service context

By the way same thing happens the other way around SQL server , IIS etc
etc
responds much faster on a Windows server machine however you can
reconfigure
XP to so that it gives prio to background services

Configuration screen , System , Advanced Tab , Top most option

HTH

Michel Posseth [MCP]

"RichG" <Ri***@discussions.microsoft.comschreef in bericht
news:E2**********************************@microso ft.com...
>I have an application written in VB.NET (Visual Studio 2003 and
Framework
1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same
code
with the same data on a Windows 2003 Server machine it takes over 3
times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any
significance.

Has anyone any experience of similar issues? What can cause it and how
do
you cure it?



Jun 27 '08 #4

P: n/a
Thanks for your suggestions, tried it but still performance 3 times longer on
W2003S.

Both the XP and W2003S machines have IIS running (V5.1 on XP and 6 on
W2003S). Both running with whatever default setting are for IIS.

Should I change IIS settings?

"Michel Posseth [MCP]" wrote:
Go to Control Panel , System , Advanced , Performance Settings , Advanced

tab. Change Processor scheduling to Programs

and lastly, change Memory usage to Programs. Now click on OK.

On equal hardware , with the same services running with equal load and the
above switches equal to XP, Windows 2003 should outperform Windows XP easy
are you sure the windows 2003 server isn`t running IIS , SQL or whatever on
the background ??

HTH

Michel


"RichG" <Ri***@discussions.microsoft.comschreef in bericht
news:12**********************************@microsof t.com...
Tried changing the configuration but it did not solve the problem. If
anything it made things worse, average time without change 12.1 sec, with
change 12.3 secs.

Any other thoughts?

"Michel Posseth [MCP]" wrote:
Strange that no one answered this question until sofar as the answer is
pretty obvious

Your program is written as an application XP gives standard priority to
user
applications a server operating system on the other hand is specially
configured to run background services
so all priority is given to background services and not to running
applications

You can do 2 things

1. reconfigure the server so that it will give prio to applications
instead
of background services
2. rewrite your program so that it runs in a service context

By the way same thing happens the other way around SQL server , IIS etc
etc
responds much faster on a Windows server machine however you can
reconfigure
XP to so that it gives prio to background services

Configuration screen , System , Advanced Tab , Top most option

HTH

Michel Posseth [MCP]

"RichG" <Ri***@discussions.microsoft.comschreef in bericht
news:E2**********************************@microsof t.com...
I have an application written in VB.NET (Visual Studio 2003 and
Framework
1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same
code
with the same data on a Windows 2003 Server machine it takes over 3
times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any
significance.

Has anyone any experience of similar issues? What can cause it and how
do
you cure it?


Jun 27 '08 #5

P: n/a
When you say identical do you mean even the processor is exactly the same?
because remember processors that look the same are not always the same... a
1.8GHz Xeon processor from a few years ago is DRASTICALLY slower then a new
1.8GHz Xeon processor in the E5xxx range... also is the memory speed the
same? CAS latency the same? all kinda issues to look at here
"RichG" <Ri***@discussions.microsoft.comwrote in message
news:E2**********************************@microsof t.com...
>I have an application written in VB.NET (Visual Studio 2003 and Framework
1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same
code
with the same data on a Windows 2003 Server machine it takes over 3 times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any
significance.

Has anyone any experience of similar issues? What can cause it and how do
you cure it?

Jun 27 '08 #6

P: n/a

"Michel Posseth [MCP]" <ms****@posseth.comschreef in bericht
news:eX**************@TK2MSFTNGP04.phx.gbl...
Strange that no one answered this question until sofar as the answer is
pretty obvious
Can it be because it has not much to do with the VB.Net language and Rich
did not write that he got no answer after trying in a more properiate
newsgroup?

:-)

Cor

Jun 27 '08 #7

P: n/a
Please suggest a more appropriate newsgroup

"Cor Ligthert[MVP]" wrote:
>
"Michel Posseth [MCP]" <ms****@posseth.comschreef in bericht
news:eX**************@TK2MSFTNGP04.phx.gbl...
Strange that no one answered this question until sofar as the answer is
pretty obvious

Can it be because it has not much to do with the VB.Net language and Rich
did not write that he got no answer after trying in a more properiate
newsgroup?

:-)

Cor
Jun 27 '08 #8

P: n/a
As far as I can tell the two machines are identical apart from the OS and the
IIS Version. They were both ordered from the same place on the same day and
look identical in all the Properties Windows.

Any suggestions welcome

"Smokey Grindel" wrote:
When you say identical do you mean even the processor is exactly the same?
because remember processors that look the same are not always the same... a
1.8GHz Xeon processor from a few years ago is DRASTICALLY slower then a new
1.8GHz Xeon processor in the E5xxx range... also is the memory speed the
same? CAS latency the same? all kinda issues to look at here
"RichG" <Ri***@discussions.microsoft.comwrote in message
news:E2**********************************@microsof t.com...
I have an application written in VB.NET (Visual Studio 2003 and Framework
1.1
SP1).

When it runs on an XP machine it takes a few seconds. Running the same
code
with the same data on a Windows 2003 Server machine it takes over 3 times
longer. The spec of the machines is identical and both are not running
anything else.

The code does nothing special and uses standard VB. It does manipulate
collections of class objects but I don't know if that is of any
significance.

Has anyone any experience of similar issues? What can cause it and how do
you cure it?


Jun 27 '08 #9

This discussion thread is closed

Replies have been disabled for this discussion.